[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1166706869.3749.29.camel@localhost>
Date: Thu, 21 Dec 2006 08:14:29 -0500
From: jamal <hadi@...erus.ca>
To: Dan Williams <dcbw@...hat.com>
Cc: stefan@...lof.de, Matthew Garrett <mjg59@...f.ucam.org>,
Michael Wu <flamingice@...rmilk.net>,
Stephen Hemminger <shemminger@...l.org>,
Arjan van de Ven <arjan@...radead.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Network drivers that don't suspend on interface down
On Wed, 2006-20-12 at 22:14 -0500, Dan Williams wrote:
...
....
> Simple == good. Down == down. Lets just agree on that and save
> ourselves a lot of pain.
netdevices have well defined operational and administrative state
machines. And very well defined relationship between operational and
administrative status. IOW, care should be invoked not to reinvent.
Power management to me seems like an operational state.
A link could only transition to operational or down depending on
whether it is "powered" up or down.
To be complete, since a netdevice is a generic construct, nota bene:
- a link could be a wireless association or ethernet cable or a PPP
session or a ATM PVC, or an infrared channel etc.
- events that result in operational link transitions could be anything
from powering up an ethernet phy with an active cable plugged to an
802.1x auth on a wireless association to a on-demand ppp link seeing an
outgoing packet.
IMO, for this discussion to be meaningful, it would be useful to read
Documentation/networking/operstates.txt
And if you are keen you can then read RFC 2863...
cheers,
jamal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists