From: Jiri Fojtasek Date: Tue, 30 Mar 2004 21:51:28 +0000 Subject: Re: [LARTC] New IMQ device implementation supporting device EOS Message-Id: <4069EBE0.2000100@hlohovec.net> List-Id: References: <40683536.4010104@hlohovec.net> In-Reply-To: <40683536.4010104@hlohovec.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Andy Furniss wrote: > Jiri Fojtasek wrote: > >> Hello Roy >> >> Roy wrote: >> >> >Hello, >> >imq became realy popular now ;) >> > > >> Sure, same as whole GNU/Linux :) >> >> >It would be good ir you wrote what is that EOS to save time for >> some people >> >on searches. >> > >> > > >> EOS - End of Send. Its time betwen two dequeues and packet transmits >> used by qdisc for calculation. > > > Is that a kernel transmit or a real "on the wire" transmit - ie can > you keep the devices' buffer empty or just detect when it's full? > > Any of current IMQ implementations do not It leave always only one packet in the device queue. It is there until is not dequeued (sent to the device driver) and then is inserted another etc, etc Jiri Zkontrolovane antivirusom ClamAv Scanned by ClamAv - http://www.clamav.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/