Date: Sat, 15 Jan 2005 05:14:26 +0000 (UTC)
From: Paul Jakma <paul@clubi.ie>
To: Peter Buckingham <peter@pantasys.com>
cc: jyri.poldre@artecdesign.ee, linux-kernel@vger.kernel.org
Subject: Re: Ethernet driver link state propagation to ip stack
In-Reply-To: <41E8155D.3020802@pantasys.com>
Message-ID: <Pine.LNX.4.61.0501150512470.15839@sheen.jakma.org>
References: <JJEGJLLALGANNBPNAIMMOEGLDGAA.jyri.poldre@artecdesign.ee>
 <41E8155D.3020802@pantasys.com>
Mail-Followup-To: paul@hibernia.jakma.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1102
Lines: 27

On Fri, 14 Jan 2005, Peter Buckingham wrote:

> I recently had similar problems (specifically with the e1000 
> driver). When one hang goes down a send to the other interface will 
> hang. This was when we were using the same socket to send on both 
> interfaces, what resulted is that the socket buffer would fill up 
> and cause the send to block. If you aren't using the same socket to 
> send out on both interfaces you should be fine. the rather large 
> hack that i used to get this to work on my system is below. 
> basically it will not enqueue a packet when the interface is down. 
> this may well do nasty things to tcp...

There's an old thread on netdev, occasionally resurrected, about this 
behaviour btw.

> peter

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
I hear what you're saying but I just don't care.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/