My votes:
> 1. What UI to provide, meaningful strings or numerical on/off?
Strings.
> I think all of us agree to have a more straightfoward UI for
> customer to
> config.
> And we have below two proposed UI so far.
> (1) flowcontrol = {send, accept, disable, both}
flowcontrol
> 2. Will we still keep our ieee802.3(5) manpage definations as
> underlying
> implementation?
Yes, I think so. Any "well defined" set is OK, this can be be ieee802
(5).
> I think before IEEE has new idea on them, we just keep them as what
> they
> are today.
> But we don't provide interfaces to directly tune them anymore. User
> still could check the
> values as read-only for debug/diag purpose.
>
> Looking forward to your suggestions.
>
> Thanks,
>
> Raymond
>
> Raymond LI - Sun Microsystems - Beijing China wrote:
>> Guys:
>>
>> Could we conclude we could implements pause control like below?
>> We want to leave ieee802.3 beneath the scene while providing user
>> with a
>> UI which makes more sense.
>>
>> /* We use 0/1 to represent "off/on" respectively. */
>>
>> Default: accept_pause = send_pause = 1;
>>
>> UI: accept_pause = 1, send_pause = 1:
>> Protocol value: cap_asmpause = 0, cap_pause = 1, adv_cap_asmpause
>> = 0,
>> adv_cap_pause = 1
>>
>> UI: accept_pause = 1, send_pause = 0:
>> Protocol value: cap_asmpause = 1, cap_pause = 0, adv_cap_asmpause
>> = 1,
>> adv_cap_pause = 0
>>
>> UI: accept_pause = 0, send_pause = 1:
>> Protocol value: cap_asmpause = 1, cap_pause = 1, adv_cap_asmpause
>> = 0,
>> adv_cap_pause = 1
>>
>> UI: accept_pause = 0, send_pause = 0:
>> Protocol value: cap_asmpause = 0, cap_pause = 0, adv_cap_asmpause
>> = 0,
>> adv_cap_pause = 0
>>
>> Please advice.
>>
>> Thanks,
>>
>> Raymond
>>
>> Raymond LI - Sun Microsystems - Beijing China wrote:
>>
>>> If we leave below for customer to set via Brussels, would it be
>>> enough?
>>>
>>> accept_pause = {0,1}
>>> send_pause = {0, 1}
>>>
>>> accept_pause = 0: Not allowed to response to pause frame
>>> accept_pause = 1: Response to pause frame, pause transmition for
>>> specified time interval
>>> send_pause = 0: Not allowed to send pause frame when congestion
>>> send_pause = 1: Sending pause frame
>>>
>>> Above are only interface we provide for customer to turn on/off
>>> pauseframe. If customer want
>>> to check properties like lp_*, adv_*, cap_*, we still provide
>>> ieee802.3
>>> ways of defination, but
>>> not tunable directly.
>>>
>>>
>>>> For older NICs, these values are tuned together. You may not have
>>>> control over whether pause frames are sent or not, in any case.
>>>>
>>>> Its also important that users can see:
>>>>
>>>> * which bits the peer is claiming support for, and
>>>> * the currently negotiated pause support
>>>>
>>>> It might be worth looking at how other operating systems expose
>>>> this
>>>> to administrators.
>>>>
>>>> -- Garrett
>>>>
>>>>
>>>>> _______________________________________________
>>>>> brussels-dev mailing list
>>>>> brussels-dev at opensolaris.org
>>>>> http://mail.opensolaris.org/mailman/listinfo/brussels-dev
>>>>>
>>>>>
>>>>>
>>> _______________________________________________
>>> networking-discuss mailing list
>>> networking-discuss at opensolaris.org
>>>
>>>
>>
>> _______________________________________________
>> networking-discuss mailing list
>> networking-discuss at opensolaris.org
>>
>
> _______________________________________________
> driver-discuss mailing list
> driver-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
--
Joost Mulders + email: joost.mulders at sun.com
Technical Specialist + phone: +31-33-45-15701
Client Solutions + fax: +31-33-45-15734
Sun Microsystems + mobile: +31-6-5198-7268
-= Anything not done right, has to be done again =-
