From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload
Date: Tue, 6 Aug 2019 08:19:21 +0000 [thread overview]
Message-ID: <VI1PR0401MB254150FE6B8BE86B11531E3289D50@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190806080206.1572-1-pbhagavatula@marvell.com>
>
> Add PTYPE to DEV_RX_OFFLOAD_* flags.
>
> Currently, most of the NICs already support PTYPE parsing and update the
> mbuf->packet_type through an internal lookup table, but there is no way to
> disable the lookup if the application is not intrested in ptypes returned by
> `rte_eth_dev_get_supported_ptypes`.
>
[Hemant] it will also mean introducing another check in datapath, if the application has asked for PTYPE offload - copy the results to mbuf->packet_type otherwise don't do it.
Your second patch is incomplete in the sense that it only adds the capability. But it does not disable the lookups?
next prev parent reply other threads:[~2019-08-06 8:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:02 pbhagavatula
2019-08-06 8:02 ` [dpdk-dev] [RFC 1/3] ethdev: add ptype as an " pbhagavatula
2019-08-06 9:00 ` Andrew Rybchenko
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 ` Hemant Agrawal [this message]
2019-08-06 8:47 ` [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload Pavan Nikhilesh Bhagavatula
2019-08-06 9:06 ` Andrew Rybchenko
2019-08-06 23:15 ` Stephen Hemminger
2019-08-07 2:04 Jerin Jacob Kollanukkaran
2019-08-07 8:32 ` Andrew Rybchenko
2019-08-07 15:22 ` Stephen Hemminger
2019-08-07 15:44 ` Andrew Rybchenko
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=VI1PR0401MB254150FE6B8BE86B11531E3289D50@VI1PR0401MB2541.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).