Project Crossbow beta release
Crossbow Flows - Update from the pre-beta Release
Crossbow beta bits can be now obtained from Download. The new features in this release are listed in What's New.
In the previous entry I talked about flow administration and some restrictions on flow properties with the pre-beta release bits. In this brief entry, I'll talk about changes to these restrictions. For more information about this release refer to Release Notes
The following are changes from the pre-beta release (Feb 2008) w.r.t properties on flows (this is based on the notes at the end of my blog entry on 02/17/2008):
Flows with a bandwidth limit can now be added to a VNIC. Additionally, the limit on a flow need not be less than the limit of its underlying link, in the sense the limit is taken just to mean an upper limit.
If a link has flows with limits, the link's bandwidth limit can be modified without having to reset the limits on its flows.
If a physical NIC has a CPU list specified, flows on that NIC can have a CPU list that is equal to or a subset of the NIC's CPU list. If a physical NIC doesn't have a CPU list specified, flows on the NIC do not have any restrictions for their CPU list.
If a physical NIC has a flow with CPU list specified, the NIC's CPU list cannot be modified. Before modifying the NIC's CPU list, all the flows on the NIC must have their CPU list reset
The issue about modifying bandwidth limit of a flow on a link without a limit is fixed.
The following notes are still relevant to the beta release:
flowadm(1m) cannot be used in a non-global zone.
CPU list cannot be specified for flows on a VNIC.
For correct behavior, flows should be added only to links that are plumbed.
After a reboot properties, if any, on a flow are not retained.
In the next entry I'll try to touch upon the additional webmin modules we have included to administer VNIC and flows.
