Thread (45 messages) 45 messages, 18 authors, 2006-12-23

Re: Network drivers that don't suspend on interface down

From: Francois Romieu <romieu@fr.zoreil.com>
Date: 2006-12-21 00:14:31
Also in: lkml

Possibly related (same subject, not in this thread)

Stephen Hemminger [off-list ref] :
[...]
   IMHO:
	When device is down, it should:
	 a) use as few resources as possible:
	       - not grab memory for buffers
	       - not assign IRQ unless it could get one
	       - turn off all power consumption possible
	 b) allow setting parameters like speed/duplex/autonegotiation,
            ring buffers, ... with ethtool, and remember the state
	 c) not accept data coming in, and drop packets queued
<nit>
Imho speed/duplex/autoneg is not the business of the device: they belong
to the phy and it's up to it to decide if its state allows to set the
requested parameters or not.
</nit>

-- 
Ueimor
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help