From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Sridhar Samudrala <sri@us.ibm.com>,
virtualization@lists.linux-foundation.org,
Jiri Pirko <jpirko@redhat.com>, Shirley Ma <xma@us.ibm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-2.6.35] virtio_net: fix oom handling on tx
Date: Mon, 21 Jun 2010 13:53:29 +0300 [thread overview]
Message-ID: <20100621105329.GA9506@redhat.com> (raw)
In-Reply-To: <201006211953.44724.rusty@rustcorp.com.au>
On Mon, Jun 21, 2010 at 07:53:43PM +0930, Rusty Russell wrote:
> On Mon, 21 Jun 2010 06:03:16 pm Michael S. Tsirkin wrote:
> > On Mon, Jun 21, 2010 at 12:13:49PM +0930, Rusty Russell wrote:
> > > - return NETDEV_TX_BUSY;
> > > + kfree_skb(skb);
> > > + return NETDEV_TX_OK;
> >
> > If we do so, let's increment the dropped counter and/or error counter?
>
> Yep, here's the extra change:
Looks good to me.
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -571,14 +571,16 @@ 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))
> + if (likely(capacity == -ENOMEM)) {
> dev_warn(&dev->dev,
> "TX queue failure: out of memory\n");
> - else
> + } else {
> + dev->stats.tx_fifo_errors++;
> dev_warn(&dev->dev,
> "Unexpected TX queue failure: %d\n",
> capacity);
> }
> + dev->stats.tx_dropped++;
> kfree_skb(skb);
> return NETDEV_TX_OK;
> }
next prev parent reply other threads:[~2010-06-21 10:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 15:20 [PATCH for-2.6.35] virtio_net: fix oom handling on tx Michael S. Tsirkin
2010-06-10 17:17 ` Sridhar Samudrala
2010-06-10 17:46 ` Stephen Hemminger
2010-06-10 17:46 ` Stephen Hemminger
2010-06-10 19:03 ` Michael S. Tsirkin
2010-06-15 4:23 ` Rusty Russell
2010-06-15 4:23 ` Rusty Russell
2010-06-21 2:43 ` Rusty Russell
2010-06-21 8:33 ` Michael S. Tsirkin
2010-06-21 10:23 ` Rusty Russell
2010-06-21 10:53 ` Michael S. Tsirkin [this message]
2010-06-21 10:53 ` Michael S. Tsirkin
2010-06-21 10:23 ` Rusty Russell
2010-06-21 8:33 ` Michael S. Tsirkin
2010-06-21 2:43 ` Rusty Russell
2010-06-10 19:03 ` Michael S. Tsirkin
2010-06-10 18:57 ` Michael S. Tsirkin
2010-06-10 18:57 ` Michael S. Tsirkin
2010-06-10 17:17 ` Sridhar Samudrala
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 15:20 Michael S. Tsirkin
2010-06-10 15:20 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=20100621105329.GA9506@redhat.com \
--to=mst@redhat.com \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=sri@us.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xma@us.ibm.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 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.