Vasumathi Sundaram wrote:
> James Carlson wrote:
>> Vasumathi Sundaram writes:
>>
>>> To cite Andrew Gallatin from the thread,
>>> "...in general, I agree there should be some way to change what
>>> stateless offloads are in use at runtime. Solaris is way behind
>>> here. For example, the BSDs do it via ifconfig (to disable
>>> TSO on "mxge0": ifconfig mxge0 -tso), Linux does it via the
>>> horribly cryptic ethtool (to disable TSO on eth2:
>>> ethtool -K eth2 tso off)."
>>>
>>
>> People may want to do it, but isn't it merely a hack?
>>
>> If TSO/LSO/mumbleSO is working right, then why would a user ever need
>> to care? Isn't this sort of like tweaking memory allocation
>> algorithms or PCI register values from the command line?
>>
>> If it's just a hack, why not expose it at a lower stability level?
>>
>>
>
> Yes, it is a hack and it can be easily handled as private properties.
> Other operating systems support this in a more obvious way and we
> thought we could provide it in Solaris too. I have no inclination
> towards one or the other.
I prefer private properties. IMO, no end user should ever be tweaking
these, unless there is a bug in the system.
- Garrett
>
>
> Vasumathi
