From: Tobias Geiger <tobias.geiger@web.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb3 & imq
Date: Mon, 12 Aug 2002 23:07:33 +0000 [thread overview]
Message-ID: <marc-lartc-102919371018574@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102892233106032@msgid-missing>
Arindam Haldar wrote:
> hi Alex,
> thanx so much.. :) .. thanx to all
> my IMQ & htb3 test rules are working ok.. the best part--> imq handling
> both in & out traffic now.. :)
I also had this setup, and i also thought of it as a "cool thing" :)
but then Patrick told me, that it's not so clever: the incoming traffic
must pass 2 qdiscs (interface-qdisc and imq-qdisc) and this is bad/not
good because
1) cpu - overhead (but this could be negleted) AND
2) these 2 qdiscs COULD drop packets and no one would know of the other
having dropped s.th. -> retransmit
ok. case 2 is not so realistic, as the qdisc on the interface normaly
is the qfifo but nevertheless point 1) and the possibility of 2) made me
think that queing double unnecessary.
>
> Alexey Talikov wrote:
>
>> Hello Arindam,
>> See imq faq http://luxik.cdi.cz/~patrick/imq/faq.html
>> Saturday, August 10, 2002, 9:46:00 AM, you wrote:
>>
>
> _______________________________________________
> 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:[~2002-08-12 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 19:45 [LARTC] htb3 & imq Arindam Haldar
2002-08-09 21:20 ` Stef Coene
2002-08-10 4:58 ` Arindam Haldar
2002-08-10 8:20 ` Stef Coene
2002-08-11 7:29 ` Arindam Haldar
2002-08-12 23:07 ` Tobias Geiger [this message]
2002-08-13 7:54 ` Stef Coene
2002-08-13 11:44 ` Arindam Haldar
2002-08-13 17:44 ` Stef Coene
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=marc-lartc-102919371018574@msgid-missing \
--to=tobias.geiger@web.de \
--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.