From: Jonathan Lundell <jlundell@lundell-bros.com>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Problem with 2.4.24 e1000 and keepalived
Date: Thu, 8 Jan 2004 17:00:42 -0800 [thread overview]
Message-ID: <p0602045cbc23ac7a1ada@[192.168.0.3]> (raw)
In-Reply-To: <20040109004525.GB545@alpha.home.local>
At 1:45am +0100 1/9/04, Willy Tarreau wrote:
> > It's unfortunate that the two conditions are conflated by most net drivers.
>
>IMHO, saying "most net drivers" is unfair : tg3, tulip, 3c59x, starfire,
>realtek, sis900, dl2k, pcnet32, and IIRC sunhme are OK. eepro100 is nearly
>OK but has this annoying bug, and only older 10 Mbps drivers don't report
>their status, often because the chip itself doesn't know.
I'm sure you're right; I should have said most of the drivers that
I'm using (including e100 &e1000).
My impression, though, is that there's a trend to use
netif_carrier_ok() to check the link in newish drivers (of course,
it's author-choice, not universal), and that the netif_carrier_ok()
is generally implemented to be dependent on the interface being
(logically) up.
It'd be nice if we could define link state reporting to be
independent of logical up/down state, at least for drivers & devices
capable of making the distinction.
--
/Jonathan Lundell.
next prev parent reply other threads:[~2004-01-09 1:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 19:05 Problem with 2.4.24 e1000 and keepalived Stephan von Krawczynski
2004-01-07 21:02 ` Willy Tarreau
2004-01-08 2:45 ` Ben Greear
2004-01-08 5:20 ` Willy Tarreau
2004-01-08 8:07 ` Ben Greear
2004-01-08 8:46 ` Willy Tarreau
2004-01-08 8:14 ` Stephan von Krawczynski
2004-01-08 8:47 ` Willy Tarreau
2004-01-08 17:49 ` Jonathan Lundell
2004-01-09 0:45 ` Willy Tarreau
2004-01-09 1:00 ` Jonathan Lundell [this message]
2004-01-09 12:18 ` Stephan von Krawczynski
2004-01-09 18:43 ` Jonathan Lundell
2004-01-09 23:56 ` Stephan von Krawczynski
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='p0602045cbc23ac7a1ada@[192.168.0.3]' \
--to=jlundell@lundell-bros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 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).