From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <pbhagavatula@marvell.com>, <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 1/3] ethdev: add ptype as an Rx offload
Date: Tue, 6 Aug 2019 12:00:19 +0300 [thread overview]
Message-ID: <798d0b07-9196-2b60-b395-ac5f01c391d7@solarflare.com> (raw)
In-Reply-To: <20190806080206.1572-2-pbhagavatula@marvell.com>
On 8/6/19 11:02 AM, pbhagavatula@marvell.com wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Add ptype to DEV_RX_OFFLOAD_* flags which can be used to enable/disable
> packet type parsing.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
I like the idea. I think there are few more Rx features which
lack Rx offload bit:
- delivery of RSS hash in mbuf (it is not always required when
RSS is used to distribute packets across Rx queues)
- maybe Rx mark, since it is an extra information which could
be passed by NIC to CPU and it is better to know in advance
at Rx queue setup if it should be requested and processed
API breakage should be considered here. I think it is OK to
introduce it in the next release cycle in a dummy way which
does not affect packet type delivery for existing PMDs
(i.e. add offload capability and advertise in PMD, but do not
take it into account when Rx mbuf is filled in) and
submit deprecation notice that it may be taken into account
by PMDs in 20.02 to avoid packet type delivery if the offload
is not requested. It will allow applications to make transition
smoother.
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-08-06 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:02 [dpdk-dev] [RFC 0/3] ethdev: add ptype as " pbhagavatula
2019-08-06 8:02 ` [dpdk-dev] [RFC 1/3] ethdev: add ptype as an " pbhagavatula
2019-08-06 9:00 ` Andrew Rybchenko [this message]
2019-08-06 14:31 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2019-08-06 15:45 ` Stephen Hemminger
2019-08-06 18:03 ` Andrew Rybchenko
2019-08-06 8:02 ` [dpdk-dev] [RFC 2/3] net: update Rx offload capabilities pbhagavatula
2019-08-06 8:02 ` [dpdk-dev] [RFC 3/3] examples: add Rx ptype offload pbhagavatula
2019-08-06 9:20 ` Ananyev, Konstantin
2019-08-06 13:57 ` Pavan Nikhilesh Bhagavatula
2019-08-06 8:19 ` [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload Hemant Agrawal
2019-08-06 8:47 ` Pavan Nikhilesh Bhagavatula
2019-08-06 9:06 ` Andrew Rybchenko
2019-08-06 23:15 ` Stephen Hemminger
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=798d0b07-9196-2b60-b395-ac5f01c391d7@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
/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).