DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Nathan Skrzypczak <nathan.skrzypczak@gmail.com>,
	andrew.rybchenko@oktetlabs.ru,
	Jakub Grajciar <jgrajcia@cisco.com>,
	dev@dpdk.org
Subject: Re: [PATCH v2] net/memif: default to physical socket
Date: Wed, 7 Dec 2022 13:01:21 -0800	[thread overview]
Message-ID: <20221207130121.5ce3fa18@hermes.local> (raw)
In-Reply-To: <625cb85c-4d10-6912-48ad-971e809da0b8@amd.com>

On Wed, 7 Dec 2022 17:15:06 +0000
Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> On 12/7/2022 3:56 PM, Nathan Skrzypczak wrote:
> > Hi Ferruh,
> >   
> 
> Hi Nathan,
> 
> > Thank you for your reply, 
> > 
> > On the potential confusion for users of the DPDK memif PMD : when
> > defaulting to abstract sockets was added in [0] (v20.10 release)
> > it did change the existing behavior, so reverting it would restore the
> > old behavior.> Also abstract sockets are quite a unusual feature in linux (a 0byte
> > prefixed string...), so I'm expecting most users of memif to just use
> > regular sockets because they're way easier to handle.
> >   
> 
> Not sure if regular socket is easier to handle, or users prefer regular
> sockets, we need more input on these.

Regular sockets are actually harder handle, it is more that users
are less familiar with them! Regular sockets have to go through
file permission checks which makes dealing with containers and SELinux
hard.  Regular sockets persist when application crashes which makes
recovery harder.

  reply	other threads:[~2022-12-07 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 10:40 [PATCH] " Nathan Skrzypczak
2022-10-17 12:12 ` [PATCH v2] " Nathan Skrzypczak
2022-12-07 15:14   ` Ferruh Yigit
2022-12-07 15:56     ` Nathan Skrzypczak
2022-12-07 17:15       ` Ferruh Yigit
2022-12-07 21:01         ` Stephen Hemminger [this message]
2022-12-08 11:24           ` Nathan Skrzypczak
2022-12-09 15:13             ` Ferruh Yigit
2023-02-07 17:26               ` Nathan Skrzypczak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221207130121.5ce3fa18@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jgrajcia@cisco.com \
    --cc=nathan.skrzypczak@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).