From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"Jerin Jacob Kollanukkaran" <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" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 1/7] ethdev: add set ptype function
Date: Tue, 1 Oct 2019 11:02:09 +0300 [thread overview]
Message-ID: <03f7f6ed-2b39-6576-ad1c-80fd981f35af@solarflare.com> (raw)
In-Reply-To: <CY4PR1801MB18632F61B7D7F26B6315F12FDE9D0@CY4PR1801MB1863.namprd18.prod.outlook.com>
On 10/1/19 10:36 AM, Pavan Nikhilesh Bhagavatula wrote:
>> -----Original Message-----
>> From: Andrew Rybchenko <arybchenko@solarflare.com>
>> Sent: Tuesday, October 1, 2019 12:34 PM
>> To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Jerin
>> Jacob Kollanukkaran <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: [EXT] Re: [dpdk-dev] [PATCH v4 1/7] ethdev: add set ptype
>> function
>> On 10/1/19 9:34 AM, pbhagavatula@marvell.com wrote:
>>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>>
>>> Add `rte_eth_dev_set_supported_ptypes` function that will allow the
>>> application to inform the PMD the packet types it is interested in.
>>> Based on the ptypes set PMDs can optimize their Rx path.
>>>
>>> -If application doesn’t want any ptype information it can call
>>> `rte_eth_dev_set_supported_ptypes(ethdev_id, RTE_PTYPE_UNKNOWN, NULL, 0)`
>>> and PMD may skip packet type processing and set rte_mbuf::packet_type to
>>> RTE_PTYPE_UNKNOWN.
>>>
>>> -If application doesn’t call `rte_eth_dev_set_supported_ptypes` PMD can
>>> return `rte_mbuf::packet_type` with `rte_eth_dev_get_supported_ptypes`.
>>> -If application is interested only in L2/L3 layer, it can inform the PMD
>>> to update `rte_mbuf::packet_type` with L2/L3 ptype by calling
>>> `rte_eth_dev_set_supported_ptypes(ethdev_id,
>>> RTE_PTYPE_L2_MASK | RTE_PTYPE_L3_MASK, NULL, 0)`.
>>> Suggested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
>>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
[snip]
>>> + if (ptype_mask & all_ptypes[i]) {
>> Should it be done if all_ptypes[i] have some bits out of ptype_mask?
>> Should set_ptypes have bits out of ptype_mask when set below?
>>
> Isn't all_ptypes[i] enum?. It makes sense if it's a bit mask.
> Get ptypes has a similar logic.
My bad. You're right.
next prev parent reply other threads:[~2019-10-01 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 7:36 Pavan Nikhilesh Bhagavatula
2019-10-01 8:02 ` Andrew Rybchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-29 21:19 [dpdk-dev] [PATCH v3 0/7] ethdev: add new Rx offload flags pbhagavatula
2019-10-01 6:34 ` [dpdk-dev] [PATCH v4 " pbhagavatula
2019-10-01 6:34 ` [dpdk-dev] [PATCH v4 1/7] ethdev: add set ptype function pbhagavatula
2019-10-01 7:04 ` 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=03f7f6ed-2b39-6576-ad1c-80fd981f35af@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).