Messages in this thread | | | Date | Wed, 20 Dec 2006 15:37:41 -0800 | From | Rick Jones <> | Subject | Re: Network drivers that don't suspend on interface down |
| |
> There are two different problems: > > 1) Behavior seems to be different depending on device driver > author. We should document the expected semantics better. > > 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
What implications does c have for something like tcpdump?
rick jones - 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/
| |