From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, dw@davidwei.uk
Subject: Re: [PATCH net-next v2] netdevsim: implement peer queue flow control
Date: Wed, 9 Jul 2025 14:36:27 -0700 [thread overview]
Message-ID: <20250709143627.5ddbf456@kernel.org> (raw)
In-Reply-To: <aG5FrObkP+S8cRZh@gmail.com>
On Wed, 9 Jul 2025 03:34:20 -0700 Breno Leitao wrote:
> On Tue, Jul 08, 2025 at 06:27:18PM -0700, Jakub Kicinski wrote:
> > On Thu, 03 Jul 2025 06:09:31 -0700 Breno Leitao wrote:
> > > +static int nsim_napi_rx(struct net_device *dev, struct nsim_rq *rq,
> > > + struct sk_buff *skb)
> > > {
> > > if (skb_queue_len(&rq->skb_queue) > NSIM_RING_SIZE) {
> > > + nsim_stop_peer_tx_queue(dev, rq, skb_get_queue_mapping(skb));
> > > dev_kfree_skb_any(skb);
> > > return NET_RX_DROP;
> > > }
> >
> > we should probably add:
> >
> > if (skb_queue_len(&rq->skb_queue) > NSIM_RING_SIZE)
> > nsim_stop_tx_queue(dev, rq, skb_get_queue_mapping(skb));
> >
> > after enqueuing the skb, so that we stop the queue before any drops
> > happen
>
> Agree, we can stop the queue when queueing the packets instead. Since we
> need to check for the queue numbers, we cannot call nsim_stop_tx_queue()
> straight away. I think we still need to have a helper
> (nsim_stop_tx_queue). This is what I have in mind:
LGTM!
> > > + if (dev->real_num_tx_queues != peer_dev->num_rx_queues)
> >
> > given that we compare real_num_tx_queues I think we should also kick
> > the queues in nsim_set_channels(), like we do in unlink_device_store()
>
> Sure. I suppose something like the following. What do you think?
>
> nsim_set_channels(struct net_device *dev, struct ethtool_channels *ch)
> {
> struct netdevsim *ns = netdev_priv(dev);
> + struct netdevsim *peer;
> int err;
>
> err = netif_set_real_num_queues(dev, ch->combined_count,
> @@ -113,6 +114,14 @@ nsim_set_channels(struct net_device *dev, struct ethtool_channels *ch)
> return err;
>
> ns->ethtool.channels = ch->combined_count;
> +
> + synchronize_net();
> + netif_tx_wake_all_queues(dev);
> + rcu_read_lock();
> + peer = rcu_dereference(ns->peer);
> + if (peer)
> + netif_tx_wake_all_queues(peer->netdev);
> + rcu_read_unlock();
That's sufficiently orthogonal to warrant a dedicated function / helper.
In terms of code I think we can skip the whole dance if peer is NULL?
> return 0;
> }
>
>
> Also, with this patch, we will eventually get the following critical
> message:
>
> net_crit_ratelimited("Virtual device %s asks to queue packet!\n", dev->name);
>
> I am wondering if that alert is not valid anymore, and I can simply
> remove it.
Ah. In nsim_setup() we should remove IFF_NO_QUEUE and stop setting
tx_queue_len to 0
next prev parent reply other threads:[~2025-07-09 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 13:09 [PATCH net-next v2] netdevsim: implement peer queue flow control Breno Leitao
2025-07-09 1:27 ` Jakub Kicinski
2025-07-09 10:34 ` Breno Leitao
2025-07-09 21:36 ` Jakub Kicinski [this message]
2025-07-11 16:29 ` Breno Leitao
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=20250709143627.5ddbf456@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).