All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New IMQ device implementation supporting device EOS
Date: Tue, 30 Mar 2004 23:51:10 +0000	[thread overview]
Message-ID: <406A07EE.7080106@dsl.pipex.com> (raw)
In-Reply-To: <40683536.4010104@hlohovec.net>

Jiri Fojtasek wrote:
> 
> 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

I think I understand - in the case of imq -> ppp -> usb/pci -> radsl 
modem with big buffer -> phone line. imq will only let one packet wait 
in ppp queue, but there could still be a full buffer in the "real" device.

Andy.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-03-30 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 14:39 [LARTC] New IMQ device implementation supporting device EOS Jiri Fojtasek
2004-03-29 18:31 ` Jiri Fojtasek
2004-03-29 19:21 ` Jiri Fojtasek
2004-03-29 20:40 ` Jiri Fojtasek
2004-03-30 10:45 ` Andy Furniss
2004-03-30 10:52 ` Andy Furniss
2004-03-30 21:51 ` Jiri Fojtasek
2004-03-30 23:51 ` Andy Furniss [this message]
2004-03-31  0:46 ` Patrick McHardy
2004-03-31  1:54 ` Roy
2004-03-31  8:13 ` Jiri Fojtasek
2004-03-31  8:27 ` Jiri Fojtasek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406A07EE.7080106@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.