DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob <jerinj@marvell.com>
Cc: <dev@dpdk.org>, David Marchand <david.marchand@redhat.com>,
	Ivan Malov <Ivan.Malov@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] doc: cleanup flow mark Rx offload deprecation notice
Date: Tue, 2 Nov 2021 14:34:15 +0000	[thread overview]
Message-ID: <964468ed-17ce-45ce-c9d5-b500cc979365@intel.com> (raw)
In-Reply-To: <a3cdca1c-6838-d620-5c82-322e28a27f0f@oktetlabs.ru>

On 11/2/2021 2:09 PM, Andrew Rybchenko wrote:
> On 11/2/21 4:47 PM, Ferruh Yigit wrote:
>> On 11/2/2021 12:50 PM, Andrew Rybchenko wrote:
>>> The problem is solved using Rx metadata delivery negotiation API [1].
>>>
>>
>> Can this API replace RX_OFFLOAD_RSS_HASH too?
> 
> It can, but it should not. RSS hash is an offload since it is a
> calculation of the hash in HW and delivery of the result to SW.
> Like checksums: check in HW and delivery of the result to SW.
> 

There is a slight difference, RSS hash is always calculated if RSS is enabled,
independent from RSS offload enabled or not.

That is why some PMDs always provides RSS hash and force enables this offload,
I would be happy to get rid of this quirk if possible.

>>
>>> [1] commit f6d8a6d3fad7 ("ethdev: negotiate delivery of packet metadata from HW to PMD")
>>>
>>> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>>> ---
>>>   doc/guides/rel_notes/deprecation.rst | 8 --------
>>>   1 file changed, 8 deletions(-)
>>>
>>> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
>>> index 4366015b01..ec5073908f 100644
>>> --- a/doc/guides/rel_notes/deprecation.rst
>>> +++ b/doc/guides/rel_notes/deprecation.rst
>>> @@ -69,14 +69,6 @@ Deprecation Notices
>>>     and the related structures (``rte_fdir_*`` and ``rte_eth_fdir_*``),
>>>     will be removed in DPDK 20.11.
>>> -* ethdev: New offload flags ``RTE_ETH_RX_OFFLOAD_FLOW_MARK`` will be added in 19.11.
>>> -  This will allow application to enable or disable PMDs from updating
>>> -  ``rte_mbuf::hash::fdir``.
>>> -  This scheme will allow PMDs to avoid writes to ``rte_mbuf`` fields on Rx and
>>> -  thereby improve Rx performance if application wishes do so.
>>> -  In 19.11 PMDs will still update the field even when the offload is not
>>> -  enabled.
>>> -
>>>   * ethdev: Announce moving from dedicated modify function for each field,
>>>     to using the general ``rte_flow_modify_field`` action.
>>>
> 


  reply	other threads:[~2021-11-02 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 12:50 Andrew Rybchenko
2021-11-02 13:47 ` Ferruh Yigit
2021-11-02 14:09   ` Andrew Rybchenko
2021-11-02 14:34     ` Ferruh Yigit [this message]
2021-11-05 16:03 ` Ferruh Yigit
2021-11-19 17:13   ` Ferruh Yigit
2021-11-22  4:10     ` Jerin Jacob
2021-11-24 12:17       ` 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=964468ed-17ce-45ce-c9d5-b500cc979365@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Ivan.Malov@oktetlabs.ru \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@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).