From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>,
Ciara Loftus <ciara.loftus@intel.com>
Cc: dev@dpdk.org, kevin.laatz@intel.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 3/3] net/af_xdp: enable support for unaligned umem chunks
Date: Tue, 22 Oct 2019 15:28:45 +0100 [thread overview]
Message-ID: <6b66518b-0e1d-2448-efed-65922be231d9@intel.com> (raw)
In-Reply-To: <20191018234815.GB44515@intel.com>
On 10/19/2019 12:48 AM, Ye Xiaolong wrote:
> On 09/30, Ciara Loftus wrote:
>> This patch enables the unaligned chunks feature for AF_XDP which allows
>> chunks to be placed at arbitrary places in the umem, as opposed to them
>> being required to be aligned to 2k. This allows for DPDK application
>> mempools to be mapped directly into the umem and in turn enable zero copy
>> transfer between umem and the PMD.
>>
>> This patch replaces the zero copy via external mbuf mechanism introduced
>> in commit e9ff8bb71943 ("net/af_xdp: enable zero copy by external mbuf").
>> The pmd_zero copy vdev argument is also removed as now the PMD will
>> auto-detect presence of the unaligned chunks feature and enable it if so
>> and otherwise fall back to copy mode if not detected.
>>
>> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
>> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
>> ---
>> doc/guides/nics/af_xdp.rst | 2 +-
>> doc/guides/rel_notes/release_19_11.rst | 4 +
>> drivers/net/af_xdp/rte_eth_af_xdp.c | 402 ++++++++++++++++++++-----
>> 3 files changed, 325 insertions(+), 83 deletions(-)
>>
>
> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
>
We tend to not split patches but since this patch doesn't depend on others, I
will get this while the discussion is going on with the other one.
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-10-22 14:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 16:42 [dpdk-dev] [PATCH v2 0/3] AF_XDP tx halt fix, IRQ pinning and unaligned chunks Ciara Loftus
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 1/3] net/af_xdp: fix Tx halt when no recv packets Ciara Loftus
2019-10-22 5:32 ` Ye Xiaolong
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 2/3] net/af_xdp: support pinning of IRQs Ciara Loftus
2019-09-30 17:11 ` Stephen Hemminger
2019-10-03 13:23 ` Loftus, Ciara
2019-10-14 14:43 ` Bruce Richardson
2019-10-21 15:24 ` Ferruh Yigit
2019-10-21 15:54 ` Bruce Richardson
2019-10-21 16:02 ` Ferruh Yigit
2019-10-21 16:14 ` Bruce Richardson
2019-10-15 11:14 ` Ray Kinsella
2019-10-21 10:04 ` Loftus, Ciara
2019-10-21 12:52 ` Varghese, Vipin
2019-10-21 13:04 ` Bruce Richardson
2019-10-21 13:11 ` Varghese, Vipin
2019-10-21 13:17 ` Bruce Richardson
2019-10-21 13:45 ` Varghese, Vipin
2019-10-21 13:56 ` Bruce Richardson
2019-10-21 14:06 ` Varghese, Vipin
2019-10-18 23:49 ` Ye Xiaolong
2019-09-30 16:42 ` [dpdk-dev] [PATCH v2 3/3] net/af_xdp: enable support for unaligned umem chunks Ciara Loftus
2019-10-18 23:48 ` Ye Xiaolong
2019-10-22 14:28 ` Ferruh Yigit [this message]
2019-10-24 11:10 ` David Marchand
2019-10-24 12:18 ` David Marchand
2019-10-24 14:18 ` 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=6b66518b-0e1d-2448-efed-65922be231d9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=xiaolong.ye@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).