From: David Marchand <david.marchand@redhat.com>
To: Ciara Loftus <ciara.loftus@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>, Xiaolong Ye <xiaolong.ye@intel.com>,
Kevin Laatz <kevin.laatz@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2 3/3] net/af_xdp: enable support for unaligned umem chunks
Date: Thu, 24 Oct 2019 13:10:18 +0200 [thread overview]
Message-ID: <CAJFAV8zBpv2JruDQiL5ujnFqEosEPW67aW1A5PNMjfUhjuFCuA@mail.gmail.com> (raw)
In-Reply-To: <20190930164205.19419-4-ciara.loftus@intel.com>
On Mon, Sep 30, 2019 at 6:45 PM Ciara Loftus <ciara.loftus@intel.com> wrote:
> diff --git a/doc/guides/rel_notes/release_19_11.rst b/doc/guides/rel_notes/release_19_11.rst
> index 06bf57c42..22369107c 100644
> --- a/doc/guides/rel_notes/release_19_11.rst
> +++ b/doc/guides/rel_notes/release_19_11.rst
> @@ -62,6 +62,8 @@ New Features
>
> * Support for pinning netdev queue IRQs to cores specified by the user.
> Available for ixgbe, i40e and mlx5 drivers.
> + * Enabled zero copy between application mempools and UMEM by enabling the
> + XDP_UMEM_UNALIGNED_CHUNKS UMEM flag.
>
>
> Removed Items
> @@ -85,6 +87,8 @@ Removed Items
> "port config <port_id> rx_offload crc_strip|scatter|ipv4_cksum|udp_cksum|tcp_cksum|
> timestamp|vlan_strip|vlan_filter|vlan_extend on|off"
>
> + * Removed AF_XDP pmd_zero copy vdev argument. Support is now auto-detected.
> +
>
Caught by Maxime, this part is indented and interpreted as a comment
when generating the doc.
Ferruh, how do you want to deal with this?
I can merge http://patchwork.dpdk.org/patch/60798/ in master for testpmd.
Or you merge it and fix the AF_XDP issue in next-net.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2019-10-24 11:10 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
2019-10-24 11:10 ` David Marchand [this message]
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=CAJFAV8zBpv2JruDQiL5ujnFqEosEPW67aW1A5PNMjfUhjuFCuA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kevin.laatz@intel.com \
--cc=maxime.coquelin@redhat.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).