From: Jakub Kicinski <kuba@kernel.org>
To: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Cc: "Mogilappagari, Sudheer" <sudheer.mogilappagari@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mkubecek@suse.cz" <mkubecek@suse.cz>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"corbet@lwn.net" <corbet@lwn.net>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH net-next v2] ethtool: add netlink based get rxfh support
Date: Mon, 14 Nov 2022 09:15:59 -0800 [thread overview]
Message-ID: <20221114091559.7e24c7de@kernel.org> (raw)
In-Reply-To: <c40e7ed0-1118-168b-7fdc-a833b461b918@intel.com>
On Sun, 13 Nov 2022 22:23:25 -0600 Samudrala, Sridhar wrote:
> > My worry is that if we go with a more broad name like
> > "queue group" someone may be mislead to adding controls
> > unrelated to flow <> queue assignment here.
>
> Later we would like to add a per queue-group parameter that would allow
> reducing/changing the number of napi pollers for a queue group from the default
> value equal to the number of queues in the queue group. Are you suggesting
> creating a queue-group object and use devlink API to configure such parameters
> for a queue-group?
I was thinking devlink because of scheduler/QoS and resource control.
For NAPI config not so sure, but either way RSS will not be a place
for NAPI/IRQ config.
next prev parent reply other threads:[~2022-11-14 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 23:42 [PATCH net-next v2] ethtool: add netlink based get rxfh support Sudheer Mogilappagari
2022-11-08 2:25 ` Jakub Kicinski
2022-11-10 0:26 ` Mogilappagari, Sudheer
2022-11-10 0:46 ` Jakub Kicinski
2022-11-10 22:08 ` Samudrala, Sridhar
2022-11-10 22:34 ` Jakub Kicinski
2022-11-10 23:24 ` Samudrala, Sridhar
2022-11-11 0:12 ` Jakub Kicinski
2022-11-14 4:23 ` Samudrala, Sridhar
2022-11-14 17:15 ` Jakub Kicinski [this message]
2022-11-15 1:46 ` Samudrala, Sridhar
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=20221114091559.7e24c7de@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=sudheer.mogilappagari@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.