[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1374852712.1666.20.camel@bwh-desktop.uk.level5networks.com>
Date: Fri, 26 Jul 2013 16:31:52 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Duan Fugang-B38611 <B38611@...escale.com>
CC: Stephen Hemminger <stephen@...workplumber.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Estevam Fabio-R49496 <r49496@...escale.com>,
"Li Frank-B20596" <B20596@...escale.com>,
Shawn Guo <shawn.guo@...aro.org>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
Hector Palacios <hector.palacios@...i.com>,
Tim Sander <tim.sander@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] net/fec: call netif_carrier_off when not having link
On Fri, 2013-07-26 at 09:35 +0000, Duan Fugang-B38611 wrote:
> On Fir, 26 Jul 2013 12:04, Stephen Hemminger wrote:
> >> diff --git a/drivers/net/ethernet/freescale/fec_main.c
> >> b/drivers/net/ethernet/freescale/fec_main.c
> >> index 0642006..631bd5a 100644
> >> --- a/drivers/net/ethernet/freescale/fec_main.c
> >> +++ b/drivers/net/ethernet/freescale/fec_main.c
> >> @@ -280,11 +280,6 @@ fec_enet_start_xmit(struct sk_buff *skb, struct net_device *ndev)
> >> unsigned short status;
> >> unsigned int index;
> >>
> >> - if (!fep->link) {
> >> - /* Link is down or auto-negotiation is in progress. */
> >> - return NETDEV_TX_BUSY;
> >> - }
> >> -
> >
> >That is a bug anyway. Since it would cause spin loop in transmit code (even without -rt).
> >If the driver cared to test it (most drivers just let hardware deal with this situation),
> >then it should free packet and return TX_OK.
>
> When link is down, the logic is
> - call netif_stop_queue() to stop queue
> - and then notify there have no link using netif_carrier_off().
netif_stop_queue() *must not* be called before netif_carrier_off(),
otherwise the TX watchdog can fire immediately. The TX watchdog only
knows when the last packet was passed to the driver, not when the queue
was stopped. The last packet could have been added an arbitrarily long
time before the link went down, therefore it may appear that the timeout
has already expired..
Although it is safe to call netif_stop_queue() after
netif_carrier_off(), it is not useful. netif_stop_queue() should only
be called from your ndo_start_xmit operation and only because the queue
is full. Any other reason to stop should be communicated to the kernel
using netif_carrier_off() or netif_device_detach().
Ben.
> But the flow must be handled in fec_enet_adjust_link() function, not in xmit().
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists