The first sentence in section 4.2 doesn't parse properly.
Otherwise it looks OK to me.
-- Garrett
Kais Belgaied wrote:
> Attached is the opinion of the Crossbow project, submitted for PSARC
> review by December 2nd 2008.
>
> Since the commitment review, the project team needed to make four minor
> changes. The changes were motivated by internal and external feed-back
> from
> early adopters and Beta customers, and by the integration with other
> consumers of the project interfaces.
>
> The changes do not constitute any architectural depart from the original
> specifications voted on, therefore, I'm including them in this opinion.
> In the case directory, final.materials has the exact specifications,
> taking into account the commitment review TCR and spec updates.
> The revised.materials directory there includes the four changes below.
> I can file a separate fasttrack to cover these changes if members
> believe it
> is necessary.
>
> - Phased delivery of the some of the resource controls.
> Initially, maxbw (maximum bandwidth), priority, cpus and fanout
> properties
> were approved for flows and datalinks.
> The support of the cpus property for flows and the fanout property for
> flows and datalinks are now targeted after the first integration.
> All other properties, are still supported, and provide sufficient added
> value for the first phase.
>
> - Add a -H option to dladm show-phys and dladm create-vnic.
> One of the projects added value is exposing a CLI to control the
> assignment
> of some of the NICs hardware resources to MAC clients (i.e. VNICs).
> At commitment time, factory MAC addresses were the only such hardware
> resource.
> The need for controlling the assignment of Receive Rings became
> increasingly
> obvious during the implementation and Beta testing, thus the -H option.
>
> - The integration with new features of LDOMs required the ability to
> allow an exclusive MAC client to set the interface's MTU,
> thus a new Consolidation Private MAC client function: mac_set_mtu().
>
> - A limitation in the multi-threadedness of a major NIC device driver
> necessitated the addition of a flag to request the serialization
> of transmit operations submitted to that driver.
> A new flag needed to be added to the Consolidation Private MAC provider
> interface (MAC_VIRT_SERIALIZE flag of the mac_register_t's m_v12n).
>
> Kais.
