netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: William Tu <witu@nvidia.com>
Cc: bodong@nvidia.com, jiri@nvidia.com, kuba@kernel.org,
	netdev@vger.kernel.org, saeedm@nvidia.com
Subject: Re: [RFC PATCH v3 net-next] Documentation: devlink: Add devlink-sd
Date: Mon, 29 Jan 2024 10:56:04 +0000	[thread overview]
Message-ID: <20240129105604.GI401354@kernel.org> (raw)
In-Reply-To: <20240125223617.7298-1-witu@nvidia.com>

On Thu, Jan 25, 2024 at 02:36:17PM -0800, William Tu wrote:
> Add devlink-sd, shared descriptor, documentation. The devlink-sd
> mechanism is targeted for configuration of the shared rx descriptors
> that server as a descriptor pool for ethernet reprsentors (reps)
> to better utilize memory. Following operations are provided:
>  * add/delete a shared descriptor pool
>  * Configure the pool's properties
>  * Bind/unbind a representor's rx channel to a descriptor pool
> 
> Propose new devlink objects because existing solutions below do
> not fit our use cases:
> 1) devlink params: Need to add many new params to support
>    the shared descriptor pool. It doesn't seem to be a good idea.
> 2) devlink-sb (shared buffer): very similar to the API proposed in
>    this patch, but devlink-sb is used in ASIC hardware switch buffer
>    and switch's port. Here the use case is switchdev mode with
>    reprensentor ports and its rx queues.
> 
> Signed-off-by: William Tu <witu@nvidia.com>
> Change-Id: I1de0d9544ff8371955c6976b2d301b1630023100
> ---
> v3: read again myself and explain NAPI context and descriptor pool
> v2: work on Jiri's feedback
> - use more consistent device name, p0, pf0vf0, etc
> - several grammar and spelling errors
> - several changes to devlink sd api
>   - remove hex, remove sd show, make output 1:1 mapping, use
>   count instead of size, use "add" instead of "create"
>   - remove the use of "we"
> - remove the "default" and introduce "shared-descs" in switchdev mode
> - make description more consistent with definitions in ethtool,
> such as ring, channel, queue.
> ---
>  .../networking/devlink/devlink-sd.rst         | 296 ++++++++++++++++++
>  1 file changed, 296 insertions(+)
>  create mode 100644 Documentation/networking/devlink/devlink-sd.rst

Hi William,

a minor nit from my side:
I think that devlink-sd should be added to the toc in index.rst.

...

  reply	other threads:[~2024-01-29 10:56 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 [this message]
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
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=20240129105604.GI401354@kernel.org \
    --to=horms@kernel.org \
    --cc=bodong@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --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 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).