lkml.org 
[lkml]   [2006]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Network drivers that don't suspend on interface down
    On Thu, 21 Dec 2006 01:11:12 +0100
    Francois Romieu <romieu@fr.zoreil.com> wrote:

    > Stephen Hemminger <shemminger@osdl.org> :
    > [...]
    > > 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>
    >

    We need to allow ethtool setting to be done before device has been brought
    up and started autonegotiation. The current MII library doesn't really support
    it.

    --
    Stephen Hemminger <shemminger@osdl.org>
    -
    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/

    \
     
     \ /
      Last update: 2006-12-21 01:29    [W:0.023 / U:62.152 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site