netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Leroy <colin@colino.net>
To: Andi Kleen <ak@suse.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	mpm@selenic.com, akpm@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Prevent netpoll hanging when link is down
Date: Fri, 8 Oct 2004 09:06:10 +0200	[thread overview]
Message-ID: <20041008090610.70d7e183@pirandello> (raw)
In-Reply-To: <20041007214505.GB31558@wotan.suse.de>

On 07 Oct 2004 at 23h10, Andi Kleen wrote:

Hi, 

> > This patch should do that. It works OK for me, but I'd like it
> > checked before sent upstream...
> > 
> > However, it doesn't fix the hang. it looks like this hang is really
> > coming from sungem.
> 
> IMHO it's not needed. Taking xmit_lock is harmless even when
> the NETIF_F_LLTX flag is set. 

Should that be completely dropped, or is it still ok ? (I think
differenciating action based on hard_start_xmit status, that is, don't
goto repeat undefinitely when NETDEV_TX_BUSY, could be a good idea).
I mean, should I rework that patch, forget about it or leave it as-is?

Concerning the hang, I see that Andrew has put my first patch, the one
checking for netif_carrier_ok(), in his tree. Is it an OK solution from
your (net dev hackers) point of view?

Thanks,
-- 
Colin

  parent reply	other threads:[~2004-10-08  7:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041006232544.53615761@jack.colino.net>
2004-10-06 21:43 ` [PATCH] Prevent netpoll hanging when link is down Matt Mackall
2004-10-07  5:53   ` Colin Leroy
2004-10-07  6:49     ` David S. Miller
2004-10-07  8:33       ` Colin Leroy
2004-10-07  8:45         ` Colin Leroy
2004-10-07 14:05       ` Colin Leroy
2004-10-07 18:28         ` David S. Miller
2004-10-07 18:41           ` Matt Mackall
2004-10-07 20:00             ` Colin Leroy
2004-10-07 18:43           ` Andi Kleen
2004-10-07 20:44           ` Colin Leroy
2004-10-07 21:45             ` Andi Kleen
2004-10-07 21:50               ` Matt Mackall
2004-10-07 22:07                 ` David S. Miller
2004-10-07 23:43                   ` Matt Mackall
2004-10-07 23:50                     ` Andi Kleen
2004-10-08  6:46                       ` Colin Leroy
2004-10-08 21:53                         ` Matt Mackall
2004-10-08  7:06               ` Colin Leroy [this message]
2004-10-08 22:00                 ` Matt Mackall
2004-10-08 22:18                   ` Andrew Morton
2004-10-11  3:59                     ` David S. Miller
2004-10-11 15:40                       ` Andi Kleen
2004-10-11 16:22                         ` Matt Mackall
2004-10-11 16:32                           ` Andi Kleen
2004-10-11 16:36                             ` Matt Mackall
2004-10-11 16:43                               ` Andi Kleen
2004-10-11 16:58                                 ` Matt Mackall
2004-10-11 17:41                                   ` Andi Kleen
2004-10-11 20:45                                   ` Colin Leroy
     [not found]                                     ` <5cac192f0410181443303379e2@mail.gmail.com>
     [not found]                                       ` <5cac192f041018145824acce5a@mail.gmail.com>
     [not found]                                         ` <20041020161119.6e30efe5@pirandello>
     [not found]                                           ` <5cac192f0410200848179ccc81@mail.gmail.com>
2004-10-21 16:36                                             ` Colin Leroy
2004-10-24 15:22                                               ` Eric Lemoine
2004-10-07 22:08             ` David S. Miller
2004-10-08  6:54               ` Colin Leroy

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=20041008090610.70d7e183@pirandello \
    --to=colin@colino.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=mpm@selenic.com \
    --cc=netdev@oss.sgi.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).