From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jakub Grajciar <jgrajcia@cisco.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/memif: use abstract socket address
Date: Fri, 9 Oct 2020 18:17:44 +0100 [thread overview]
Message-ID: <8073c7b5-373e-c1c1-8aee-538d152570ed@intel.com> (raw)
In-Reply-To: <20201009165859.5303-1-jgrajcia@cisco.com>
On 10/9/2020 5:58 PM, Jakub Grajciar wrote:
> Abstract socket address has no connection with
> filesystem pathnames and the socket disappears
> once all open references are closed.
>
> Memif pmd will use abstract socket address by default.
> For backwards compatibility use new argument
> 'socket-abstract=no'
>
> Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com>
> ---
> doc/guides/nics/memif.rst | 1 +
> drivers/net/memif/memif_socket.c | 28 +++++++++++++++++--------
> drivers/net/memif/rte_eth_memif.c | 34 ++++++++++++++++++++++++++++++-
> drivers/net/memif/rte_eth_memif.h | 10 +++++----
> 4 files changed, 60 insertions(+), 13 deletions(-)
looks good thanks, can you also add a release notes update for the feature?
next prev parent reply other threads:[~2020-10-09 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:39 [dpdk-dev] [PATCH] net/memif: use abstract socket address Jakub Grajciar
2020-10-05 13:09 ` Ferruh Yigit
2020-10-05 15:23 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
2020-10-05 18:17 ` Stephen Hemminger
2020-10-06 8:59 ` Ferruh Yigit
2020-10-07 10:00 ` [dpdk-dev] [PATCH v2] " Jakub Grajciar
2020-10-09 16:58 ` [dpdk-dev] [PATCH v3] " Jakub Grajciar
2020-10-09 17:17 ` Ferruh Yigit [this message]
2020-10-12 8:28 ` [dpdk-dev] [PATCH v4] " Jakub Grajciar
2020-10-12 14:57 ` Ferruh Yigit
2020-10-12 15:17 ` Stephen Hemminger
2020-10-07 15:03 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2020-10-09 15:09 ` Ferruh Yigit
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=8073c7b5-373e-c1c1-8aee-538d152570ed@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.