DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, Ciara Loftus <ciara.loftus@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/1] net/af_xdp: shared UMEM support
Date: Wed, 23 Sep 2020 07:34:38 +0000	[thread overview]
Message-ID: <20200923073439.12485-1-ciara.loftus@intel.com> (raw)

This patch integrates support for shared UMEMs into the AF_XDP PMD.
The feature is currently available in the linux-next tree [1] and
should be available in the v5.10 kernel.

Detailed information on the shared UMEM feature can be found in the
kernel documentation.

Support for the kernel feature is detected in DPDK by querying the
LINUX_KERNEL_VERSION and ensuring a kernel >= 5.10.0. Since this
kernel is not yet released, if one wishes to test this patch now it
is suggested to use the aforementioned linux-next tree and modify the
version check to align with the version of that tree. Once the kernel
is released (~December) this will no longer be necessary.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=acabf32805f7

Ciara Loftus (1):
  net/af_xdp: shared UMEM support

 doc/guides/nics/af_xdp.rst          |   6 +-
 drivers/net/af_xdp/compat.h         |  41 ++++
 drivers/net/af_xdp/meson.build      |   4 +
 drivers/net/af_xdp/rte_eth_af_xdp.c | 302 ++++++++++++++++++++++------
 4 files changed, 289 insertions(+), 64 deletions(-)
 create mode 100644 drivers/net/af_xdp/compat.h

-- 
2.17.1


             reply	other threads:[~2020-09-23  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  7:34 Ciara Loftus [this message]
2020-09-23  7:34 ` [dpdk-dev] [PATCH v3 1/1] " Ciara Loftus
2020-09-24 15:30   ` 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=20200923073439.12485-1-ciara.loftus@intel.com \
    --to=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).