From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
kys@microsoft.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH 1/1] net/hyperv: Fix the code handling tx busy
Date: Mon, 19 Mar 2012 10:48:47 -0700 [thread overview]
Message-ID: <20120319104847.3a4c5fc0@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1332177118.9397.32.camel@edumazet-glaptop>
On Mon, 19 Mar 2012 10:11:58 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Mon, 2012-03-19 at 10:02 -0700, Haiyang Zhang wrote:
> > Instead of dropping the packet, we keep the skb buffer, and return
> > NETDEV_TX_BUSY to let upper layer retry send. This will not cause
> > endless loop, because the host is taking data away from ring buffer.
> >
> > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > Reviewed-by: K. Y. Srinivasan <kys@microsoft.com>
> > ---
> > drivers/net/hyperv/netvsc_drv.c | 5 +----
> > 1 files changed, 1 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/net/hyperv/netvsc_drv.c
> > index 2517d20..dd29478 100644
> > --- a/drivers/net/hyperv/netvsc_drv.c
> > +++ b/drivers/net/hyperv/netvsc_drv.c
> > @@ -223,13 +223,10 @@ static int netvsc_start_xmit(struct sk_buff *skb, struct net_device *net)
> > net->stats.tx_bytes += skb->len;
> > net->stats.tx_packets++;
> > } else {
> > - /* we are shutting down or bus overloaded, just drop packet */
> > - net->stats.tx_dropped++;
> > kfree(packet);
> > - dev_kfree_skb_any(skb);
> > }
> >
> > - return NETDEV_TX_OK;
> > + return ret ? NETDEV_TX_BUSY : NETDEV_TX_OK;
> > }
> >
> > /*
>
> Thats simply not true at all.
>
> A start_xmit() cannot do that.
>
> TX_BUSY should never be returned at all, its a deprecated code, for
> pretty good reasons. (assuming queue is not stopped)
>
> Try this on a machine with one CPU, I am pretty sure this can trigger
> complete freezes.
>
> Once softirq loops in your start_xmit(), how do you think one process
> can help you now ?
Eric is right, look how devices with real physical rings work.
They test for space left at end of start xmit and stop the transmit
queue with netif_stop_queue. The transmit done code then re-enables
when enough space is netif_wake_queue. Think of it as classic
high/low water mark on a FIFO.
next prev parent reply other threads:[~2012-03-19 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 17:02 [PATCH 0/1] net/hyperv: Fix the code handling tx busy Haiyang Zhang
2012-03-19 17:02 ` [PATCH 1/1] " Haiyang Zhang
2012-03-19 17:11 ` Eric Dumazet
2012-03-19 17:46 ` Haiyang Zhang
2012-03-19 17:46 ` Haiyang Zhang
2012-03-19 18:23 ` Eric Dumazet
2012-03-19 17:48 ` Stephen Hemminger [this message]
2012-03-19 17:50 ` Haiyang Zhang
2012-03-19 18:30 ` Eric Dumazet
2012-03-19 19:17 ` Haiyang Zhang
2012-03-19 19:17 ` Haiyang Zhang
2012-03-19 20:46 ` Eric Dumazet
2012-03-19 20:50 ` Haiyang Zhang
2012-03-19 20:50 ` Haiyang Zhang
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=20120319104847.3a4c5fc0@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=eric.dumazet@gmail.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--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.