From: Jakub Kicinski <kuba@kernel.org>
To: "Nambiar, Amritha" <amritha.nambiar@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
"jhs@mojatatu.com" <jhs@mojatatu.com>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
"Gomes, Vinicius" <vinicius.gomes@intel.com>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Subject: Re: [net-next PATCH v2 0/4] Extend action skbedit to RX queue mapping
Date: Thu, 22 Sep 2022 05:29:08 -0700 [thread overview]
Message-ID: <20220922052908.4b5197d9@kernel.org> (raw)
In-Reply-To: <MWHPR11MB1293C87E3EC9BD7D64829F2FF14E9@MWHPR11MB1293.namprd11.prod.outlook.com>
On Thu, 22 Sep 2022 08:19:07 +0000 Nambiar, Amritha wrote:
> > Alex pointed out that it'd be worth documenting the priorities of
> > aRFS vs this thing, which one will be used if HW matches both.
>
> Sure, I will document the priorities of aRFS and TC filter selecting
> the Rx queue. On Intel E810 devices, the TC filter selecting Rx queue
> has higher priority over aRFS (Flow director filter) if both the filters
> are matched.
Is it configurable? :S If we think about RSS context selection we'd
expect the context to be selected based on for example the IPv6 daddr
of the container but we still want aRFS to select the exact queue...
Is there a counterargument for giving the flow director higher prio?
next prev parent reply other threads:[~2022-09-22 12:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 1:23 [net-next PATCH v2 0/4] Extend action skbedit to RX queue mapping Amritha Nambiar
2022-09-08 1:24 ` [net-next PATCH v2 1/4] act_skbedit: Add support for action skbedit " Amritha Nambiar
2022-09-08 1:24 ` [net-next PATCH v2 2/4] act_skbedit: Offload skbedit queue mapping for receive queue Amritha Nambiar
2022-09-08 1:24 ` [net-next PATCH v2 3/4] ice: Enable RX queue selection using skbedit action Amritha Nambiar
2022-09-08 1:24 ` [net-next PATCH v2 4/4] Documentation: networking: TC queue based filtering Amritha Nambiar
2022-09-08 17:34 ` kernel test robot
2022-09-08 15:27 ` [net-next PATCH v2 0/4] Extend action skbedit to RX queue mapping Alexander Duyck
2022-09-09 9:18 ` Nambiar, Amritha
2022-09-09 18:35 ` Alexander Duyck
2022-09-15 8:45 ` Nambiar, Amritha
2022-09-15 15:21 ` Alexander Duyck
2022-09-15 22:09 ` Nambiar, Amritha
2022-09-16 15:58 ` Alexander Duyck
2022-09-21 20:29 ` Jakub Kicinski
2022-09-22 8:19 ` Nambiar, Amritha
2022-09-22 12:29 ` Jakub Kicinski [this message]
2022-09-23 1:09 ` Nambiar, Amritha
2022-09-23 13:02 ` Jakub Kicinski
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=20220922052908.4b5197d9@kernel.org \
--to=kuba@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=amritha.nambiar@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@gmail.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).