I'm submitting this fast-track for Venugopal Iyer.  The release binding 
is Patch, but this case depends on the following other cases:

PSARC/2009/364 dlstat and flowstat
PSARC/2009/448 pool dladm link property
PSARC/2009/501 Dynamic Ring Grouping on NICs

This case makes modifications to the above cases which have not yet 
integrated (in other words, there are no incompatible changes introduced 
due to the fact that these cases will all be integrated simultaneously).

All new command-line options are Committed, and link properties 
introduced are Uncommitted.

Updated man pages and man page diffs for dladm(1M), dlstat(1M), and 
flowstat(1M) are available in the case directory under "materials".

Update to PSARC/2009/501
------------------------

The values for rxrings and txrings properties are changed to support
NICs such as bge and ixgbe for which we cannot explicitly specify the
number of rings.

Thus, the proposed values for rxrings and txrings properties are:

    sw : This link does not need any hardware rings of the
         specified type (RX or TX)

    hw : This link needs at least 1 hardware ring of the
         specified type (RX or TX)

    x > 0 : This link needs x rings of the specified type (RX or TX).

Additionally, in order to keep the names of the properties consistent
and easier to understand, the read-only properties are changed to:

    rxrings-available: The total number of RX rings available for use,
         i.e. not exclusively given to any MAC client.

    txrings-available: The total number of TX rings available for use.

    rxhwclnt-available: The total number of additional RX
         hardware-based MAC clients that can be created. Each of these
         hardware-based MAC client could have one or more RX rings
         assigned to them.

    txhwclnt-available: The total number of additional TX
         hardware-based MAC clients that can be created. Each of these
         hardware-based MAC clients could have one or more TX rings
         assigned to them.

The value for rxrings or txrings could be set to "sw" or "hw" based on
the values of the read-only properties rxhwclnt-available or
txhwclnt-available for the underlying device. Further, the read-only
property rxrings-available or txrings-available, if not zero,
indicates the number of rings that can be assigned to the rxrings and
txrings properties.

E.g if rxhwclnt-available is 0, then only "sw" links can be created,
if not, it specifies the number of "hw" links that can be created.  If
a link is created as "hw", then the actual number of rings that gets
assigned to the link depends on the underlying NIC. If it is ixgbe or
bge, then the number of rings assigned to the link is determined from
parameters defined at attach time of the device (e.g. via
driver.conf).

Some NICs like nxge allows users to specify the number of rings
required for a link. Thus, a link created with "hw" is given one
hardware ring by default. If the link needs more rings, then it can be
specified in the rxrings or txrings property. The number of rings
available can be obtained from the read-only properties
rxhwclnt-available or txhwclnt-available.

In order to display the actual number of rings that gets assigned to a
link created with "hw", we introduce two read-only properties -
rxrings-effective and txrings-effective.


Update to PSARC/2009/364
------------------------

New option is added to dlstat(1m) and flowstat [-a | -A] to display
all statistics.  Additionally, the examples in the man page are
modified (from the ones in the original PSARC case
documents). Additionally, we also replace the b and B specifier for -u
option with R (Raw) since bits (b) and Bytes (B) is not very
meaningful for packet counts.


Update to PSARC/2009/448
------------------------

Adding read-only properties for effective pool and cpus. The existing
'cpus' and new 'pool' data link properties indicate the
administrator's intent but are only effective when the datapath is
setup and for 'pool', when pools are enabled.

The 'cpus-effective' and 'pools-effective' read-only properties will
show which cpus and pools are being used for the link.

Reply via email to