venugopal iyer wrote: > > On Thu, 24 Jan 2008, David Edmondson wrote: > > >> In looking at the flowadm.1m manual page (from npt.sfbay) we see: >> >> FLOW PROPERTIES >> >> The following flow properties are supported. Note that >> the ability to set a given property to a given value depends >> on the driver and hardware. >> >> >> maxbw Sets the full duplex bandwidth for the link. The >> bandwidth is specified as an integer with one of the >> scale suffixes(K, M, or G for Kbps, Mbps, and Gbps). >> >> priority >> Sets the relative priority for the link. The value may >> be given as one of the tokens rt(real time), high, >> normal, >> or low. >> >> cpus Bind the processing of packets for a given flow to >> a processor or a set of processors. The value can be >> a comma separated list of one or more processor id. >> If the list consists of more than one processor, >> the processing will spread out to all the processors >> although connection to processor affinity and packet >> ordering for packets of any individual connection will >> be maintained. >> >> The processor or set of processors are not exclusively >> reserved for the network device. Only the kernel >> threads and interrupt associated with processing of >> the device are bound to the processor or the set of >> processor specified. In case, it is desired that >> processors be dedicated to the device, psrset(1M) can >> be used to create a processor_set and then >> specifiying the processors from the processor_set to >> bind the device to. >> >> If the link was already bound to processor or set >> of processors due to a previous operation, the binding >> will be removed and the new set of processors will be >> used instead. >> >> Shouldn't the word 'link' be replaced with 'flow' in most (all?) >> cases? >> > > Yes. > > cut and paste (w/o changes) problem. i'll take care of that. >> I'm only really interested in setting properties on flows that >> represent a whole link (there's no need to partition the traffic). The >> flowadm syntax appears to require that I provide some attributes. Is >> that correct? >> > > Yes. I am not sure I understand "flows that represent a whole link". You > don't want to assign the property to the link itself? > #dladm set-linkprop will allow you to do this.
-mike
