An updated version of the Vanity Naming and Nemo Unification design
document is now available at:

   http://opensolaris.org/os/community/networking/uv-design.pdf

Comments are welcome. I've updated the document according to all
the review comments received. Below highlights some of the issues
raised during review and our proposed solutions:

 a. The "DL_CAPAB_UNBOUNDED_PKT" capability

    This has been changed to a DL_IOC_VLAN_CAPAB ioctl. The driver
    will acknowledge this ioctl if it can handle the extra VLAN tag
    bytes. This ioctl will not be used to address the Jumbo frame
    issue which mentioned by Paul Jakma, since that problem should
    be fixed by changing the driver to report the correct maximum
    SDU in its DL_INFO_ACK.

 b. show-aggr

    Although Nicolas requested to provide an example of the new
    show-aggr output, the show-aggr subcommand is different from
    the other show-* subcommands because it displays more than one
    level of objects (the aggregation and the aggregated links). It
    is not optimal to have a "nested" table like today because we'd
    like the output to be machine-parsing-friendly. We are still in
    the discussion regarding this and the document will be updated
    once we reach agreement.

 c. discard-phys

    This subcommand has been changed to delete-phys.

 d. PPP devices (sppp0 etc.)

    PPP devices will not be managed under softmac because they are
    not associated with any hardware,  are created on demands
    and don't have any devfs nodes. That said, if it is necessary to
    make PPP devices GLDv3 devices one day (for example, if we
    decide to move the whole stack above TCP/IP away from DLPI),
    the design does not prohibit the future changes to unify the PPP
    devices under Nemo.

 e. diskless boot

    A new section 6.3.3 has been added to discuss the interaction
    between diskless boot and vanity naming.

 f. interrupt coalescing

    Several reviewers raised their concerns regarding the performance
    benefit of the "soft" interrupt coalescing. We will prototype this
    and evaluate the performance impact, then decide what to do. For
    now the document has been left as it was.

Thanks
- Cathy
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to