Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb v3 not as good as htb v2?
Date: Wed, 08 Oct 2003 14:11:30 +0000	[thread overview]
Message-ID: <marc-lartc-106562246000917@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106562149532078@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

I've used HTB and CBQ to protect MPEG2 traffic streams from UDP traffic
over 100 Mb/s interfaces.  I have not yet attempted this with 1000 Mb/s
interfaces, but I hope to get to that this year (it it much more
difficult to measure accurately at this speed).

On Wed, 2003-10-08 at 09:49, Anton Yurchenko wrote:
> Hello,
> 
> I`ve been using htb v2 for more then a year without any major problems. 
> Recently I needed to upgrade to newer kernel becouse of non LARTC 
> related issues. After installing 2.4.22 when the htb qdisc was attached 
> to the interface even without any rules, I was not able to send more 
> ~1mbit through the interface. After I reversed the htb3 patch and 
> rebuild with htb2 everything works as normal. Has anyone experienced the 
> same issue? thanks
-- 
    Lawrence MacIntyre     865.574.8696     lpz@ornl.gov
               Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-10-08 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 13:49 [LARTC] htb v3 not as good as htb v2? Anton Yurchenko
2003-10-08 14:03 ` nuclearcat
2003-10-08 14:11 ` Lawrence MacIntyre [this message]
2003-10-08 16:56 ` Wilfried Weissmann
2003-10-09  8:44 ` Anton Yurchenko
2003-10-09 16:45 ` 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-106562246000917@msgid-missing \
    --to=lpz@ornl.gov \
    --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