Luigi Rizzo wrote: > the signal that tell the WFQ algorithm when you can transmit the > next packet comes from the pipe. The latter ticks either at a > predefined rate (as configured with the 'bw NNN bit/s' parameter), > or from the tx interrupt coming from a device (e.g. you can say > something like 'bw ed0' to get the transmit clock from device ed0). > > HOWEVER: i have implemented the necessary machinery in dummynet (it > is a function called if_tx_rdy()) and in the user interface, "ipfw", > but have not added the hooks to call if_tx_rdy() in each device > driver because these calls are somewhat expensive, and you probably do not want > them on a 100Mbit/s interface. > > See http://www.geocrawler.com/archives/3/165/2002/3/0/8222181/ > on how to use them (a search for "dummynet if_tx_rdy()" should return > some results).
I'm trying to merge this into the sis driver, which seems to batch transmissions together. For clarification, do you expect one if_tx_rdy() call per packet or one per batch? Per packet may result in a burst of these calls, does dummynet handle this? Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
