Raymond LI wrote: > Garrett, > > Let's put the discuss in a wider society. Attachment is the original > mail thread. We are very interested to know what Solaris society > thinks about current setting ways and what are their expections. > > Raymond > > ------------------------------------------------------------------------ > > Subject: > pause bits (802.3x) and brussels > From: > Garrett D'Amore <Garrett.Damore at sun.com> > Date: > Thu, 05 Jul 2007 09:55:20 -0700 > To: > brussels-iteam at sun.com, clearview-iteam at sun.com > > To: > brussels-iteam at sun.com, clearview-iteam at sun.com > > > One set of properties that I would dearly love to see Brussels > simplify, are the adv_pause and adv_asympause bits. The definitions > of what these bits mean (and their brethren, link_pause, > link_asym_pause, etc.) are baroque in the extreme. I suspect that > this may have come about as a result of IEEE 802.3x trying to > "compress" the number of bits used in the actual MII autonegotiation > registers. > > It would be far, far simpler, IMO, to simply have two sets of tunables > for end users: > > one set representing TX direction pause (cap, adv, lp, state) > one set representing RX direction pause (cap, adv, lp, state) > > Ultimately, for some device drivers, it will turn out that this is > simpler to code for anyway. > Could we introduce below property into Brussels while keeping current IEEE802.3 defination? Having a property named "ether-flow-ctrl", which has below possible values:
ether-flow-ctrl = 0: Disable pause frame flow control ether-flow-ctrl = 1: Enable just Rx flow control ether-flow-ctrl = 2: Enable just Tx flow control ether-flow-ctrl = 3: Enable both Rx/Tx flow control Please advice. Thanks, Raymond
