> -----Original Message----- > From: Ferruh Yigit <ferruh.yi...@intel.com> > Sent: Monday, October 5, 2020 3:09 PM > To: Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco) > <jgraj...@cisco.com>; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] net/memif: use abstract socket address > > On 10/5/2020 1:39 PM, Jakub Grajciar wrote: > > Abstract socket address has no connection with filesystem pathnames > > and the socket dissapears once all open references are closed. > > > > Memif pmd will use abstract socket address by default. > > For backwards compatibility use new argument 'socket-abstract=no' > > > > Why this backward compatibility is required? How the end user affected from > swithching to abstract sockets? > Since when linux supports abstract sockets, does this switch will cause > problem > with old kernel versions? > > Is there any benefit of the abstract sockets other than socket cleaned > automatically (I assume for unix sockets it is done when file filesystem > reference > removed)? >
What I mean by this is compatibility with other implementations and older versions of the driver, e.g. vpp and libmemif don't support abstract socket yet.
