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 10:45:18 +0000 [thread overview]
Message-ID: <40694FBE.2060206@dsl.pipex.com> (raw)
In-Reply-To: <40683536.4010104@hlohovec.net>
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
> use it, so the calculation by qdisc may not be correct, whish causing
> filling physical device fifos without control. In devices with variable
> speed (WiFi, Modems) it causes overload because the physisal trafics is
> out of control. It happen only on busy boxes, like my routers where is
> about 70 ppl at once. In a simply test enviroment this issue will never
> happen.
>
> >and it would be good if you posted source code directly (not inside of
> diff
> >file)
> >for review purposes
> >
> > >
> The whole patch contain only few new files, all other are patches of the
> original kernel files. BTW Midnight Comander 4.6.0 contain very nice
> diff virtual filesystem, so you can browse .diff files like a tar archive.
>
> >also you can look at my imq version, because it is much easer to develop
> >since is independent from kernel.
> >and does not need to patch it.
> >http://pupa.da.ru/imq/
> >
> > >
> I have play with with your version :) Having independet implementation
> is nice idea. I play with that idea too but it was more dificult to have
> stable solution in short time i need and with EOS support its quite
> imposible ...
>
> 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/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-30 10:45 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 [this message]
2004-03-30 10:52 ` Andy Furniss
2004-03-30 21:51 ` Jiri Fojtasek
2004-03-30 23:51 ` Andy Furniss
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=40694FBE.2060206@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.