From: Alex Kiselev <alex@therouter.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] RSS hash based on L2 (src mac, dst mac) on Intel 82599 NICs
Date: Tue, 18 Dec 2018 21:45:11 +0300 [thread overview]
Message-ID: <CB547585-0885-42F9-BD25-09F72A5D7D6F@therouter.net> (raw)
In-Reply-To: <20181218103605.2f69f403@xeon-e3>
I think I should describe the problem I am trying to solve.
I am looking for a way to use RSS for PPPoE traffic.
Using RSS calculation based on L2 is one way. It can be
done using specific x710 API. And it looks like the DDP
is event a better way to do so, but it's also supported
only on intel 700 series NICs. So, I am looking for
a solution to spread PPPoE flows to different queues
on x520 or mellanox NICs.
> On 18 Dec 2018, at 21:36, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Tue, 18 Dec 2018 20:02:06 +0300
> Alex Kiselev <alex@therouter.net> wrote:
>
>> Hi.
>>
>> Is it possible to configure Intel 82599 NICs RSS function to calculate rss hash value
>> based on only the L2 src address and dst address for nonIp packets?
>>
>> It's possible to do so with Intel x710 cards, but I haven't found the same feature
>> for 82599. Have I missed something? Or it's a unique feature available only on x710
>> cards?
>>
>> Thanks.
>>
>
> In DPDK this is ETH_RSS_L2_PAYLOAD.
> The ixgbe driver does not list this is a supported offload type:
>
> #define IXGBE_RSS_OFFLOAD_ALL ( \
> ETH_RSS_IPV4 | \
> ETH_RSS_NONFRAG_IPV4_TCP | \
> ETH_RSS_NONFRAG_IPV4_UDP | \
> ETH_RSS_IPV6 | \
> ETH_RSS_NONFRAG_IPV6_TCP | \
> ETH_RSS_NONFRAG_IPV6_UDP | \
> ETH_RSS_IPV6_EX | \
> ETH_RSS_IPV6_TCP_EX | \
> ETH_RSS_IPV6_UDP_EX)
>
> The Linux driver does not appear to support this either.
prev parent reply other threads:[~2018-12-18 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 17:02 Alex Kiselev
2018-12-18 18:36 ` Stephen Hemminger
2018-12-18 18:45 ` Alex Kiselev [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=CB547585-0885-42F9-BD25-09F72A5D7D6F@therouter.net \
--to=alex@therouter.net \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.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).