From: eth <eth@finsiel.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Has anybody used HTB?
Date: Fri, 08 Mar 2002 12:54:41 +0000 [thread overview]
Message-ID: <marc-lartc-101561805702776@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101540571724934@msgid-missing>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Martin Devera wrote:<br>
<blockquote type="cite" cite="mid:Pine.LNX.4.10.10203081156510.15162-100000@luxik.cdi.cz">
<blockquote type="cite">
<pre wrap="">I've tc-ed ICMP to be 1:110, ssh to be 1:120 and the rest 1:130. Guess <br>what? Look at the following example, you can notice that although ICMP <br>should be the highest prio, sometimes it's not. Maybe I've made, again, <br>some mistakes or maybe prio from HTB needs more tuning... :)<br></pre>
</blockquote>
<pre wrap=""><!----><br>It is possible. On what hw you did the test ? 10Mbit eth ? If yes then<br>there is possible to have approx 2ms jitter in delay because you can<br>go in when large FTP packet is already in transit.</pre>
</blockquote>
You guessed right, I was on 10Mbit ethernet. Then again, how did PRIO managed
to make it happen?<br>
<br>
Wait a second. Can't we... I mean you... make a decision to stop sending
the pending packet if something more important has just arrived? I guess
not... giving a seconf thought it's like once the driver has "spited" the
bytes in the NIC's hardware buffer they're gone for good... unless there
is a standard in the kernel to say "Stop now nomatter what".<br>
<br>
If things are like you say the smaller the MTU the smaller the effect, right?<br>
<blockquote type="cite" cite="mid:Pine.LNX.4.10.10203081156510.15162-100000@luxik.cdi.cz">
<pre wrap="">You can try to do hierarchy of htb/prio/htb but from my side of view<br>I'd rather repair htb's priorization if there is bug ;)<br></pre>
</blockquote>
Well... it'll be nice to have an htb option with 0 to 9 with 0 being the
most draconian in terms of prio and lousy in terms of bucketing and 9 the
oposite. But again I'm not in your's shoes... ;-)<br>
<br>
</body>
</html>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-08 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 9:05 [LARTC] Has anybody used HTB? eth
2002-03-06 9:20 ` Martin Devera
2002-03-06 14:48 ` eth
2002-03-08 10:09 ` Martin Devera
2002-03-08 10:49 ` eth
2002-03-08 11:35 ` Martin Devera
2002-03-08 12:54 ` eth [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-101561805702776@msgid-missing \
--to=eth@finsiel.ro \
--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.