From: Rusty Russell <rusty@rustcorp.com.au>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] virtio_net: Fix queue full check
Date: Fri, 29 Oct 2010 20:17:24 +1030 [thread overview]
Message-ID: <201010292017.25099.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20101028051036.25340.23442.sendpatchset@krkumar2.in.ibm.com>
On Thu, 28 Oct 2010 03:40:36 pm Krishna Kumar wrote:
> I get many queue full errors being wrongly reported when running
> parallel netperfs:
>
> Oct 17 10:22:40 localhost kernel: net eth0: Unexpected TX queue failure: -28
> Oct 17 10:28:22 localhost kernel: net eth0: Unexpected TX queue failure: -28
> Oct 17 10:35:58 localhost kernel: net eth0: Unexpected TX queue failure: -28
> Oct 17 10:41:06 localhost kernel: net eth0: Unexpected TX queue failure: -28
>
> I initially changed the check from -ENOMEM to -ENOSPC, but
> virtqueue_add_buf can return only -ENOSPC when it doesn't have
> space for new request. Patch removes redundant checks but
> displays the failure errno.
>
> Signed-off-by: Krishna Kumar <krkumar2@in.ibm.com>
> ---
> drivers/net/virtio_net.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
> diff -ruNp org/drivers/net/virtio_net.c new/drivers/net/virtio_net.c
> --- org/drivers/net/virtio_net.c 2010-10-11 10:20:02.000000000 +0530
> +++ new/drivers/net/virtio_net.c 2010-10-21 17:37:45.000000000 +0530
> @@ -570,17 +570,10 @@ static netdev_tx_t start_xmit(struct sk_
>
> /* This can happen with OOM and indirect buffers. */
> if (unlikely(capacity < 0)) {
> - if (net_ratelimit()) {
> - if (likely(capacity == -ENOMEM)) {
> - dev_warn(&dev->dev,
> - "TX queue failure: out of memory\n");
> - } else {
> - dev->stats.tx_fifo_errors++;
> - dev_warn(&dev->dev,
> - "Unexpected TX queue failure: %d\n",
> - capacity);
> - }
> - }
> + if (net_ratelimit())
> + dev_warn(&dev->dev,
> + "TX queue failure (%d): out of memory\n",
> + capacity);
Hold on... you were getting -ENOSPC, which shouldn't happen. What makes you
think it's out of memory?
Confused,
Rusty.
next prev parent reply other threads:[~2010-10-29 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 5:10 [PATCH] virtio_net: Fix queue full check Krishna Kumar
2010-10-29 9:47 ` Rusty Russell [this message]
2010-10-29 10:55 ` Krishna Kumar2
2010-10-29 11:28 ` Rusty Russell
2010-11-02 16:17 ` Michael S. Tsirkin
2010-11-04 12:24 ` Michael S. Tsirkin
2010-11-04 16:17 ` Krishna Kumar2
2010-11-04 16:45 ` Michael S. Tsirkin
2010-11-07 23:08 ` Rusty Russell
2010-11-09 4:26 ` Krishna Kumar2
2010-11-09 13:15 ` Michael S. Tsirkin
2010-11-09 15:30 ` Krishna Kumar2
2010-11-09 15:30 ` Michael S. Tsirkin
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=201010292017.25099.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--cc=netdev@vger.kernel.org \
/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.