From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>
Subject: Re: RTE_ETH_RSS_IP support by Intel NIC drivers
Date: Fri, 20 Jun 2025 11:31:45 +0100 [thread overview]
Message-ID: <aFU4kWSK5mn4XPmS@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FD17@smartserver.smartshare.dk>
On Fri, Jun 20, 2025 at 12:24:24PM +0200, Morten Brørup wrote:
> Don't the Intel i40e and e1000 drivers support RSS on IP addresses [1]?
> It looks like they do, but don't report it.
>
> For i40e:
> Accepted: 0x2288 FRAG_IPV4 NONFRAG_IPV4_OTHER FRAG_IPV6 NONFRAG_IPV6_OTHER
> Unsupported: 0x8104 IPV4 IPV6 IPV6_EX
>
That looks like a miss on our part. I'll log an internal bug and we can
investigate.
> For e1000:
> Accepted: 0x8104 IPV4 IPV6 IPV6_EX
> Unsupported: 0x2288 FRAG_IPV4 NONFRAG_IPV4_OTHER FRAG_IPV6 NONFRAG_IPV6_OTHER
>
The e1000 driver, is actually a small collection of slightly different, but
related drivers for 1G HW - some of which are quite basic. I'm not sure
what the specific capabilities of the various HW NICs are, but again, we'll
take a look and see if we are missing some things.
> The RSS offload types [2] have no descriptions, so it's hard to guess which alternatives would be viable.
>
> [1]: https://elixir.bootlin.com/dpdk/v25.03/source/lib/ethdev/rte_ethdev.h#L783
> [2]: https://elixir.bootlin.com/dpdk/v25.03/source/lib/ethdev/rte_ethdev.h#L553
>
> -Morten
>
prev parent reply other threads:[~2025-06-20 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:24 Morten Brørup
2025-06-20 10:31 ` Bruce Richardson [this message]
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=aFU4kWSK5mn4XPmS@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).