DPDK patches and discussions
 help / color / mirror / Atom feed
From: taozj888  <taozj888@163.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re:Re: [PATCH v3 1/2] examples/l3fwd: relax RSS requirement with option
Date: Mon, 13 Nov 2023 19:47:01 +0800 (CST)	[thread overview]
Message-ID: <2645794b.6331.18bc881a674.Coremail.taozj888@163.com> (raw)
In-Reply-To: <20231112153349.202150ff@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

At 2023-11-13 07:33:49, "Stephen Hemminger" <stephen@networkplumber.org> wrote:
>On Sun, 12 Nov 2023 07:16:10 +0000
>Trevor Tao <taozj888@163.com> wrote:
>
>> Now the port Rx mq_mode had been set to RTE_ETH_MQ_RX_RSS
>> by default, but some hw and/or virtual interface does not
>> support the RSS and offload mode presupposed, e.g., some
>> virtio interfaces in the cloud don't support
>> RSS and the error msg may like:
>> 
>> virtio_dev_configure(): RSS support requested but not supported by
>> the device
>> Port0 dev_configure = -95
>> 
>> So to enable the l3fwd running in that environment, the Rx mode requirement
>> can be relaxed to reflect the hardware feature reality here, and the l3fwd
>> can run smoothly then.
>> 
>> An option named "relax-rx-mode" is added to enable the relax action
>> here, and it's disabled by default.
>> 
>> Signed-off-by: Trevor Tao <taozj888@163.com>
>
>Doesn't need to be an option. The application can just look at the offload
>flags and quickly determine that if multiple queues are being used than
>RSS is required. If device doesn't support RSS, then fallback to single

>queue with a warning.


Hi Stephen:


I think the option here was suggested/required by Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>.
The discussion thread is listed below:


">>>>Should we probably instead have a new commnad-line option to explicitly 
>>>>disable RSS?
>>> 
>>>>Something like: '--no-rss' or so?
>>> Trevor: the RSS capability for a certain port was got by the rte_eth_dev_info_get() automatically, and we think the user should not care about its status beforehand, but if it's missing, a warning notification for the degrade here would be proposed to make it run smoothly.
>>
>>Personally, I still think it would be better the user will
>>have an ability to disable it explicitly.
>>Same as l3fwd does now with 'parse-ptype'.

>>
"


Thanks,


Trevor Tao

[-- Attachment #2: Type: text/html, Size: 3157 bytes --]

  reply	other threads:[~2023-11-13 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  7:16 [PATCH v3 0/2] example/l3fwd: relax l3fwd rx RSS/Offload if needed Trevor Tao
2023-11-12  7:16 ` [PATCH v3 1/2] examples/l3fwd: relax RSS requirement with option Trevor Tao
2023-11-12 23:33   ` Stephen Hemminger
2023-11-13 11:47     ` taozj888 [this message]
2023-11-13 12:40       ` Morten Brørup
2023-11-13 13:19         ` Konstantin Ananyev
2023-11-13 16:06           ` taozj888
2023-11-12  7:16 ` [PATCH v3 2/2] examples/l3fwd: relax the Offload requirement Trevor Tao

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=2645794b.6331.18bc881a674.Coremail.taozj888@163.com \
    --to=taozj888@163.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).