From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: William Tu <witu@nvidia.com>,
Jacob Keller <jacob.e.keller@intel.com>,
bodong@nvidia.com, jiri@nvidia.com, netdev@vger.kernel.org,
saeedm@nvidia.com,
"aleksander.lobakin@intel.com" <aleksander.lobakin@intel.com>
Subject: Re: [RFC PATCH v3 net-next] Documentation: devlink: Add devlink-sd
Date: Tue, 20 Feb 2024 14:17:09 -0800 [thread overview]
Message-ID: <20240220141709.42a9c640@kernel.org> (raw)
In-Reply-To: <ZdMaCfWRf9qpDSGR@nanopsycho>
On Mon, 19 Feb 2024 10:06:17 +0100 Jiri Pirko wrote:
> >Gluing to the device is easier, IIUC, once the pool is create we can
> >give it whatever attributes we want. devlink ID, bus/device, netdev,
> >IOMMU domain, anything.
>
> I'm confused. Above (***) you say that the shared pool is created upon
> first netdev creation. Now you indicate the user creates it and then
> "binds" it to some object (like devlink).
>
> So, do you think there should be 2 types of pools:
> 1) implicit upon netdev creation
> 2) explicit defined by the user?
Implicitly, "once the pool is create[d]" does not say that user created
the pool. The flow would be more like:
- user changes configuration "rules"
- if device is running && config changed:
- core instantiates the new pools
- core issues "reset" request to the device to rebuild queues
- core shuts down old pools
next prev parent reply other threads:[~2024-02-20 22:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 4:56 [RFC PATCH v2 net-next] Documentation: devlink: Add devlink-sd William Tu
2024-01-25 21:12 ` [RFC PATCH v3 " William Tu
2024-01-25 22:36 ` William Tu
2024-01-29 10:56 ` Simon Horman
2024-01-29 22:23 ` William Tu
2024-01-31 1:07 ` Jakub Kicinski
2024-01-31 18:47 ` William Tu
2024-01-31 19:06 ` Jakub Kicinski
2024-01-31 19:16 ` William Tu
2024-01-31 20:45 ` Jakub Kicinski
2024-01-31 21:37 ` William Tu
2024-01-31 21:41 ` Jacob Keller
2024-01-31 22:30 ` Jakub Kicinski
2024-01-31 23:02 ` William Tu
2024-01-31 23:17 ` Jakub Kicinski
2024-02-01 2:23 ` Samudrala, Sridhar
2024-02-01 14:00 ` William Tu
2024-02-02 8:48 ` Michal Swiatkowski
2024-02-02 15:27 ` William Tu
2024-02-01 10:13 ` Jiri Pirko
2024-02-02 4:00 ` Jakub Kicinski
2024-02-02 7:46 ` Jiri Pirko
2024-02-09 1:26 ` Jakub Kicinski
2024-02-15 13:19 ` Jiri Pirko
2024-02-15 17:41 ` Jacob Keller
2024-02-16 2:07 ` Jakub Kicinski
2024-02-16 8:15 ` Jiri Pirko
2024-02-16 21:42 ` Jacob Keller
2024-02-16 21:47 ` Jacob Keller
2024-02-19 8:59 ` Jiri Pirko
2024-02-16 8:10 ` Jiri Pirko
2024-02-16 21:44 ` Jacob Keller
2024-02-16 1:58 ` Jakub Kicinski
2024-02-16 8:06 ` Jiri Pirko
2024-02-17 2:43 ` Jakub Kicinski
2024-02-19 9:06 ` Jiri Pirko
2024-02-20 22:17 ` Jakub Kicinski [this message]
2024-02-01 19:16 ` William Tu
2024-02-02 3:30 ` Jakub Kicinski
2024-02-02 4:26 ` William Tu
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=20240220141709.42a9c640@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=bodong@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=witu@nvidia.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.