From: Yasuhiro Ohara <yasu@nttv6.jp>
To: bruce.richardson@intel.com
Cc: dev@dpdk.org, beilei.xing@intel.com
Subject: Re: ETH_RSS_IP only does not seem to balance traffic
Date: Fri, 14 Jan 2022 10:41:26 +0900 (JST) [thread overview]
Message-ID: <20220114.104126.1937264055616251633.yasu@nttv6.jp> (raw)
In-Reply-To: <YeA/0SQjcKJpCBu9@bricha3-MOBL.ger.corp.intel.com>
That makes sense. Thank you.
It would be great to have further comments from the maintener.
For the RTE framework integrity, would it be better for us
to have a consistent meaning for the ETH_RSS_XXX flags?
Do the other drivers act differently?
Best regards,
Yasu
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: ETH_RSS_IP only does not seem to balance traffic
Date: Thu, 13 Jan 2022 15:05:53 +0000
Message-ID: <YeA/0SQjcKJpCBu9@bricha3-MOBL.ger.corp.intel.com>
> On Thu, Jan 13, 2022 at 12:52:04AM +0900, Yasuhiro Ohara wrote:
>>
>> Hi,
>>
>> My system developper friend recently ran into a problem where
>> l3fwd does not appear to receive balanced traffic on Intel XL710,
>> but it is resolved when the attached patch is applied.
>>
>> - .rss_hf = ETH_RSS_IP,
>> + .rss_hf = ETH_RSS_IP | ETH_RSS_TCP | ETH_RSS_UDP,
>>
>> IIRC I ran into a similar problem 3 or 4 years back,
>> but didn't report then because I believed I was doing something silly.
>> But since my friend is an experienced engineer, I feel like
>> it may be better (for the community) to ask this in the list.
>>
>> We are using dpdk-stable-18.11.6 and igb_uio.
>>
>> What are we doing wrong?
>>
>> If it is not a FAQ, I can test it again with more recent stable,
>> and will report the details.
>>
> For XL710 NICs, I believe that ETH_RSS_IP load balances only IP frames that
> do not have TCP or UDP headers also. Adding i40e driver maintainer on CC
> to comment further.
>
> /Bruce
>
next prev parent reply other threads:[~2022-01-14 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 15:52 Yasuhiro Ohara
2022-01-13 15:05 ` Bruce Richardson
2022-01-14 1:41 ` Yasuhiro Ohara [this message]
2022-01-14 1:44 ` Xing, Beilei
2022-01-14 1:55 ` Yasuhiro Ohara
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=20220114.104126.1937264055616251633.yasu@nttv6.jp \
--to=yasu@nttv6.jp \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).