From: Matt Johnston <matt@codeconstruct.com.au>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
Jinliang Wang <jinliangw@google.com>
Cc: William Kennington <wak@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mctp-i2c: increase the MCTP_I2C_TX_WORK_LEN to 500
Date: Fri, 17 Nov 2023 08:50:18 -0600 [thread overview]
Message-ID: <39c213c17712fdc8877b4277b430bfded71c3cca.camel@codeconstruct.com.au> (raw)
In-Reply-To: <bd01e1544e388eb71b8713e94ea2165d1a805b54.camel@codeconstruct.com.au>
Hi,
On Fri, 2023-11-17 at 15:29 +0800, Jeremy Kerr wrote:
> spin_lock_irqsave(&midev->tx_queue.lock, flags);
> if (skb_queue_len(&midev->tx_queue) >= MCTP_I2C_TX_WORK_LEN) {
> netif_stop_queue(dev);
> spin_unlock_irqrestore(&midev->tx_queue.lock, flags);
> netdev_err(dev, "BUG! Tx Ring full when queue awake!\n");
> return NETDEV_TX_BUSY;
> }
>
> __skb_queue_tail(&midev->tx_queue, skb);
> if (skb_queue_len(&midev->tx_queue) == MCTP_I2C_TX_WORK_LEN) // normal stop
> netif_stop_queue(dev);
> spin_unlock_irqrestore(&midev->tx_queue.lock, flags);
>
> What looks like has happened here:
>
> 1) we have TX_WORK_LEN-1 packets queued
> 2) we release a flow, which queues the "marker" skb. the tx_queue now
> has TX_WORK_LEN items
> 3) we queue another packet, ending up with TX_WORK_LEN+1 in the queue
> 4) the == TX_WORK_LEN test fails, so we dont do a netif_stop_queue()
>
> A couple of potential fixes:
>
> * We do the check and conditional netif_stop_queue() in (2)
> * We change the check there to be `>= MCTP_I2C_TX_WORK_LEN`
My inclination would be to change the second comparison (the normal stop
condition) to
/* -1 to allow space for an additional unlock_marker skb */
if (skb_queue_len(&midev->tx_queue) >= MCTP_I2C_TX_WORK_LEN-1)
Cheers,
Matt
prev parent reply other threads:[~2023-11-17 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 7:04 [PATCH] mctp-i2c: increase the MCTP_I2C_TX_WORK_LEN to 500 Jinliang Wang
2023-11-17 7:29 ` Jeremy Kerr
2023-11-17 14:50 ` Matt Johnston [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=39c213c17712fdc8877b4277b430bfded71c3cca.camel@codeconstruct.com.au \
--to=matt@codeconstruct.com.au \
--cc=jinliangw@google.com \
--cc=jk@codeconstruct.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wak@google.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).