From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>, <dev@dpdk.org>
Cc: <matan@mellanox.com>, <rasland@mellanox.com>,
<thomas@monjalon.net>, <ferruh.yigit@intel.com>,
<jerinjacobk@gmail.com>, <stephen@networkplumber.org>,
<ajit.khaparde@broadcom.com>, <maxime.coquelin@redhat.com>,
<olivier.matz@6wind.com>, <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce changes to ethdev rxconf structure
Date: Wed, 5 Aug 2020 14:14:43 +0300 [thread overview]
Message-ID: <5fc9b97b-3b02-1f9f-9acd-333a92585d58@solarflare.com> (raw)
In-Reply-To: <1596617395-29271-1-git-send-email-viacheslavo@mellanox.com>
On 8/5/20 11:49 AM, Viacheslav Ovsiienko wrote:
> The DPDK datapath in the transmit direction is very flexible.
> The applications can build multi-segment packets and manages
> almost all data aspects - the memory pools where segments
> are allocated from, the segment lengths, the memory attributes
> like external, registered, etc.
>
> In the receiving direction, the datapath is much less flexible,
> the applications can only specify the memory pool to configure
> the receiving queue and nothing more. The packet being received
> can only be pushed to the chain of the mbufs of the same data
> buffer size and allocated from the same pool. In order to extend
> the receiving datapath buffer description it is proposed to add
> the new fields into rte_eth_rxconf structure:
>
> struct rte_eth_rxconf {
> ...
> uint16_t rx_split_num; /* number of segments to split */
> uint16_t *rx_split_len; /* array of segment lengths */
> struct rte_mempool **mp; /* array of segment memory pools */
> ...
> };
>
> The non-zero value of rx_split_num field configures the receiving
> queue to split ingress packets into multiple segments to the mbufs
> allocated from various memory pools according to the specified
> lengths. The zero value of rx_split_num field provides the
> backward compatibility and queue should be configured in a regular
> way (with single/multiple mbufs of the same data buffer length
> allocated from the single memory pool).
>
> The new approach would allow splitting the ingress packets into
> multiple parts pushed to the memory with different attributes.
> For example, the packet headers can be pushed to the embedded data
> buffers within mbufs and the application data into the external
> buffers attached to mbufs allocated from the different memory
> pools. The memory attributes for the split parts may differ
> either - for example the application data may be pushed into
> the external memory located on the dedicated physical device,
> say GPU or NVMe. This would improve the DPDK receiving datapath
> flexibility preserving compatibility with existing API.
>
> The proposed extended description of receiving buffers might be
> considered by other vendors to be involved into similar features
> support, it is the subject for the further discussion.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Acked-by: Jerin Jacob <jerinjacobk@gmail.com>
I"m OK with the idea in general and we'll work on details
in the next release cycle.
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2020-08-05 11:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 10:58 [dpdk-dev] [PATCH] " Viacheslav Ovsiienko
2020-08-03 11:56 ` Jerin Jacob
2020-08-03 13:06 ` Slava Ovsiienko
2020-08-04 13:32 ` Jerin Jacob
2020-08-05 6:35 ` Slava Ovsiienko
2020-08-06 15:58 ` Ferruh Yigit
2020-08-06 16:25 ` Stephen Hemminger
2020-08-06 16:41 ` Jerin Jacob
2020-08-06 17:03 ` Slava Ovsiienko
2020-08-06 18:10 ` Stephen Hemminger
2020-08-07 11:23 ` Slava Ovsiienko
2020-08-03 14:31 ` [dpdk-dev] ***Spam*** " Andrew Rybchenko
2020-08-06 16:15 ` [dpdk-dev] " Ferruh Yigit
2020-08-06 16:29 ` Slava Ovsiienko
2020-08-06 16:37 ` Ferruh Yigit
2020-08-06 16:39 ` Slava Ovsiienko
2020-08-06 16:43 ` Ferruh Yigit
2020-08-06 16:48 ` Slava Ovsiienko
2020-08-05 8:49 ` [dpdk-dev] [PATCH v2] " Viacheslav Ovsiienko
2020-08-05 11:14 ` Andrew Rybchenko [this message]
2020-08-06 12:39 ` Thomas Monjalon
2020-08-06 21:42 ` Thomas Monjalon
2020-08-06 16:31 ` Ferruh Yigit
2020-08-06 17:00 ` Slava Ovsiienko
2020-08-06 16:55 ` [dpdk-dev] [PATCH v2] doc: fix the release notes for Mellanox PMD Viacheslav Ovsiienko
2020-08-06 17:12 ` Asaf Penso
2020-08-06 22:37 ` Thomas Monjalon
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=5fc9b97b-3b02-1f9f-9acd-333a92585d58@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=rasland@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.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).