From: Jakub Kicinski <kuba@kernel.org>
To: Alexander H Duyck <alexander.duyck@gmail.com>
Cc: "Nambiar, Amritha" <amritha.nambiar@intel.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, Saeed Mahameed <saeed@kernel.org>,
"Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Subject: Re: Kernel interface to configure queue-group parameters
Date: Wed, 8 Feb 2023 16:36:34 -0800 [thread overview]
Message-ID: <20230208163634.51ee1fa8@kernel.org> (raw)
In-Reply-To: <c8476530638a5f4381d64db0e024ed49c2db3b02.camel@gmail.com>
On Tue, 07 Feb 2023 08:28:56 -0800 Alexander H Duyck wrote:
> I think much of this depends on exactly what functionality we are
> talking about.
Right, maybe we need to take a page out of the container's book and
concede that best we can do is provide targeted APIs for slices of
the problem. Which someone in user space would have to combine.
> > 4. Devlink:
> > Pros:
> > - New parameters can be added without any changes to the kernel or
> > userspace.
> >
> > Cons:
> > - Queue/Queue_group is a function-wide entity, Devlink is for
> > device-wide stuff. Devlink being device centric is not suitable for
> > queue parameters such as rates, NAPI etc.
>
> Yeah, I wouldn't expect something like this to be a good fit.
Devlink has the hierarchical rate API for example.
Maybe we should (re)consider adding top level nodes for RSS contexts
there?
next prev parent reply other threads:[~2023-02-09 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 0:15 Kernel interface to configure queue-group parameters Nambiar, Amritha
2023-02-07 16:28 ` Alexander H Duyck
2023-02-09 0:36 ` Jakub Kicinski [this message]
2023-02-16 10:34 ` Nambiar, Amritha
2023-02-16 10:35 ` Nambiar, Amritha
2023-02-16 17:32 ` Jakub Kicinski
2023-02-24 9:14 ` Nambiar, Amritha
2023-02-24 19:22 ` Jakub Kicinski
2023-02-19 17:39 ` Alexander H Duyck
2023-02-24 9:17 ` Nambiar, Amritha
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=20230208163634.51ee1fa8@kernel.org \
--to=kuba@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=sridhar.samudrala@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 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).