From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/1] net/af_xdp: shared UMEM support
Date: Thu, 24 Sep 2020 16:30:23 +0100 [thread overview]
Message-ID: <b448d146-7d39-71ec-b5c6-e3759a6ab14d@intel.com> (raw)
In-Reply-To: <20200923073439.12485-2-ciara.loftus@intel.com>
On 9/23/2020 8:34 AM, Ciara Loftus wrote:
> Kernel v5.10 will introduce the ability to efficiently share a UMEM
> between AF_XDP sockets bound to different queue ids on the same or
> different devices. This patch integrates that functionality into the AF_XDP
> PMD.
>
> A PMD will attempt to share a UMEM with others if the shared_umem=1 vdev
> arg is set. UMEMs can only be shared across PMDs with the same mempool, up
> to a limited number of PMDs goverened by the size of the given mempool.
> Sharing UMEMs is not supported for non-zero-copy (aligned) mode.
>
> The benefit of sharing UMEM across PMDs is a saving in memory due to not
> having to register the UMEM multiple times. Throughput was measured to
> remain within 2% of the default mode (not sharing UMEM).
>
> A version of libbpf >= v0.2.0 is required and the appropriate pkg-config
> file for libbpf must be installed such that meson can determine the
> version.
Tested providing the devarg when kernel/library support is not there
cause gracefully exit. Not able to test the functionality, relying Ciara
on it.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-09-24 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 7:34 [dpdk-dev] [PATCH v3 0/1] " Ciara Loftus
2020-09-23 7:34 ` [dpdk-dev] [PATCH v3 1/1] " Ciara Loftus
2020-09-24 15:30 ` Ferruh Yigit [this message]
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=b448d146-7d39-71ec-b5c6-e3759a6ab14d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
/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).