From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Krishna Kumar2 <krkumar2@in.ibm.com>,
davem@davemloft.net, netdev@vger.kernel.org, yvugenfi@redhat.com
Subject: Re: [PATCH] virtio_net: Fix queue full check
Date: Tue, 2 Nov 2010 18:17:30 +0200 [thread overview]
Message-ID: <20101102161730.GA32311@redhat.com> (raw)
In-Reply-To: <201010292158.40411.rusty@rustcorp.com.au>
On Fri, Oct 29, 2010 at 09:58:40PM +1030, Rusty Russell wrote:
> On Fri, 29 Oct 2010 09:25:09 pm Krishna Kumar2 wrote:
> > Rusty Russell <rusty@rustcorp.com.au> wrote on 10/29/2010 03:17:24 PM:
> >
> > > > 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?
> >
> > virtqueue_add_buf_gfp returns only -ENOSPC on failure, whether
> > direct or indirect descriptors are used, so isn't -ENOSPC
> > "expected"? (vring_add_indirect returns -ENOMEM on memory
> > failure, but that is masked out and we go direct which is
> > the failure point).
>
> Ah, OK, gotchya.
> I'm not even sure the fallback to linear makes sense; if we're failing
> kmallocs we should probably just return -ENOMEM. Would mean we can
> tell the difference between "out of space" (which should never happen
> since we stop the queue when we have < 2+MAX_SKB_FRAGS slots left)
> and this case.
>
> Michael, what do you think?
>
> Thanks,
> Rusty.
Let's make sure I understand the issue: we use indirect buffers
so we assume there's still a lot of place in the ring, then
allocation for the indirect fails and so we return -ENOSPC?
So first, I agree it's a bug. But I am not sure killing the fallback
is such a good idea: recovering from add buf failure is hard
generally, we should try to accomodate if we can. Let's just fix
the return code for now?
And generally, we should be smarter: as long as the ring is almost
empty, and s/g list is short, it is a waste to use indirect buffers.
BTW we have had a FIXME there for a long while, I think Yan suggested
increasing that threshold to 3. Yan?
Further, maybe preallocating some memory for the indirect buffers might
be a good idea.
In short, lots of good ideas, let's start with the minimal patch that is
a good 2.6.37 candidate too. How about the following (untested)?
virtio: fix add_buf return code for OOM
add_buff returned ENOSPC on out of memory: this is a bug
as at leats virtio-net expects ENOMEM and handles it
specially. Fix that.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index 1475ed6..0a89098 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring.c
@@ -165,7 +165,7 @@ int virtqueue_add_buf_gfp(struct virtqueue *_vq,
{
struct vring_virtqueue *vq = to_vvq(_vq);
unsigned int i, avail, uninitialized_var(prev);
- int head;
+ int head = -ENOSPC;
START_USE(vq);
@@ -191,7 +191,7 @@ int virtqueue_add_buf_gfp(struct virtqueue *_vq,
if (out)
vq->notify(&vq->vq);
END_USE(vq);
- return -ENOSPC;
+ return head;
}
/* We're about to use some buffers from the free list. */
--
MST
next prev parent reply other threads:[~2010-11-02 16:17 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
2010-10-29 10:55 ` Krishna Kumar2
2010-10-29 11:28 ` Rusty Russell
2010-11-02 16:17 ` Michael S. Tsirkin [this message]
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=20101102161730.GA32311@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=yvugenfi@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).