From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cbq vs htb?
Date: Thu, 22 May 2003 21:11:30 +0000 [thread overview]
Message-ID: <marc-lartc-105363815500764@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105301464526654@msgid-missing>
On Thursday 15 May 2003 19:17, Intercom - Roberto Ravetti wrote:
> What I have told you, about the problem of ping delay with CBQ, is just
> with RF Conection..
I don't know how a RF connections is physical seen by the kernel. Htb does
not care about the physical link so maybe better suited to shape on a RF
connection.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-22 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 16:01 [LARTC] cbq vs htb? Griem, Hans T
2003-05-15 17:00 ` Stef Coene
2003-05-15 17:17 ` Intercom - Roberto Ravetti
2003-05-15 18:13 ` Griem, Hans T
2003-05-15 18:26 ` Stef Coene
2003-05-22 21:11 ` Stef Coene [this message]
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-105363815500764@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox