[EMAIL PROTECTED] wrote:
> On (11/08/07 20:41), Darren Reed wrote:
>
>> More than a few people have argued against exposing the capabilities
>> of NICs and/or allowing users to change them...see below for what our
>> users actually *want* to do.
>>
>
> The approach that the related projects in this area
> seem to be heading towards is that we
> identify the "interesting" capabilities via properties, and use
> set/get linkprop to find the info that Dale is looking for. I do
> agree that we have to do some work to get this ability
> into the GUI.
>
The idea of exposing the status of the capability makes sense, if only
because it helps users figure out how their device will perform.
However, with th exception of jumbo frames (which necessarily need to be
tunable), I don't think the other properties (such as various hardware
offloads) should be "tunable". At least not in something as general
purpose as the GUI.
At the moment, the only features which customers really *need* to know
about are:
1) link speed/duplex abilities
2) mtu restrictions
3) vlan support (not tunable, just viewable)
The other features, such as 802.3ad and IP instances, will be taken care
of by Clearview, so that customers will cease asking those questions
once all NICs provide a GLDv3 interface.
-- Garrett
> --Sowmini
>
>
>> From: Dale Ghent <[EMAIL PROTECTED]>
>> One other thing aside from MTU - capabilities of specific chipsets out
>> there range widely, even within the same product family (eg, BCM
>> NetXtreme 56xx/57xx). It would be nice if dladm and the GUI provided a
>> run down of what the driver will do for a respective chipset so as to
>> answer admin's questions such as "Does my NIC support jumbo frames?",
>> "Can it do VLAN tagging?", "Can it do 802.3ad?", "Does it sport a
>> TOE?" It would be very nice if dladm and the GUI could provide this
>> information easily since the first step in setting a property is
>> knowing if you're capable of doing it in the first place.
>>
>> /dale
>>
> _______________________________________________
> networking-discuss mailing list
> [email protected]
>
_______________________________________________
networking-discuss mailing list
[email protected]