netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Donald Hunter <donald.hunter@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, Jonathan Corbet <corbet@lwn.net>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org,
	Gal Pressman <gal@nvidia.com>, Moshe Shemesh <moshe@nvidia.com>,
	Carolina Jubran <cjubran@nvidia.com>,
	Cosmin Ratiu <cratiu@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next 00/14] devlink and mlx5: Support cross-function rate scheduling
Date: Mon, 24 Nov 2025 18:43:32 -0800	[thread overview]
Message-ID: <20251124184332.317a652f@kernel.org> (raw)
In-Reply-To: <f828d5d5-6ba3-4e9c-a7fb-3a0193f7e9bf@gmail.com>

On Sun, 23 Nov 2025 08:57:58 +0200 Tariq Toukan wrote:
> I submitted the code before my weekend as we have a gap of ~1.5 working 
> days (timezones + Friday). It could be utilized for collecting feedback 
> on the proposed solution, or even get it accepted.

Makes sense, our recommendation is to throw in an RFC in the subjects
in this case. Saves the back and forth.

      reply	other threads:[~2025-11-25  2:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 13:09 [PATCH net-next 00/14] devlink and mlx5: Support cross-function rate scheduling Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 01/14] devlink: Reverse locking order for nested instances Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 02/14] documentation: networking: add shared devlink documentation Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 03/14] devlink: Add helpers to lock nested-in instances Tariq Toukan
2025-11-20 14:52   ` Jiri Pirko
2025-11-20 13:09 ` [PATCH net-next 04/14] devlink: Refactor devlink_rate_nodes_check Tariq Toukan
2025-11-20 14:53   ` Jiri Pirko
2025-11-20 13:09 ` [PATCH net-next 05/14] devlink: Decouple rate storage from associated devlink object Tariq Toukan
2025-11-20 14:55   ` Jiri Pirko
2025-11-20 13:09 ` [PATCH net-next 06/14] devlink: Add parent dev to devlink API Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 07/14] devlink: Allow parent dev for rate-set and rate-new Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 08/14] devlink: Allow rate node parents from other devlinks Tariq Toukan
2025-11-20 14:55   ` Jiri Pirko
2025-11-20 13:09 ` [PATCH net-next 09/14] net/mlx5: Introduce shared devlink instance for PFs on same chip Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 10/14] net/mlx5: Expose a function to clear a vport's parent Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 11/14] net/mlx5: Store QoS sched nodes in the sh_devlink Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 12/14] net/mlx5: qos: Support cross-device tx scheduling Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 13/14] net/mlx5: qos: Enable cross-device scheduling Tariq Toukan
2025-11-20 13:09 ` [PATCH net-next 14/14] net/mlx5: Document devlink rates Tariq Toukan
2025-11-21  3:39 ` [PATCH net-next 00/14] devlink and mlx5: Support cross-function rate scheduling Jakub Kicinski
2025-11-23  6:57   ` Tariq Toukan
2025-11-25  2:43     ` Jakub Kicinski [this message]

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=20251124184332.317a652f@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cjubran@nvidia.com \
    --cc=corbet@lwn.net \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=ttoukan.linux@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).