netdev
[Top] [All Lists]

Re: Why /sys/class/net/*/features is read-only?

To: "Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx>
Subject: Re: Why /sys/class/net/*/features is read-only?
From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Mon, 23 May 2005 13:55:16 -0700
Cc: netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.62.0505232346310.17855@xxxxxxxxxxxxxxxxxxx>
Organization: Open Source Development Lab
References: <Pine.LNX.4.62.0505201346420.29305@xxxxxxxxxxxxxxxxxxx> <20050523092827.7883af33@xxxxxxxxxxxxxxxxx> <Pine.LNX.4.62.0505232346310.17855@xxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 23 May 2005 23:49:57 +0300 (EEST)
"Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx> wrote:

> On Mon, 23 May 2005, Stephen Hemminger wrote:
> 
> > On Mon, 23 May 2005 10:46:50 +0300 (EEST)
> > "Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx> wrote:
> >
> >> Hello!
> >>
> >> Why features file is read-only. If an admin want to force some attributes,
> >> we can let them, right?
> >>
> >
> > Leave it read-only because the hardware may not want to allow them on that 
> > flavor and so it would
> > have to be device specific.
> 
> You are clear right for hardware devices, but for software ones (bridge 
> for example) it makes sense. Anyway, only admin can change them.
> 
> If you have a bridge with 5 net cards and 4 supports SG, some people 
> may want to force SG on the bridge.

Then implement ethtool on the bridge device, it wouldn't be hard to do that.

<Prev in Thread] Current Thread [Next in Thread>