From: "Vik Heyndrickx" <vik.heyndrickx@pandora.be>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Re: priomap table
Date: Sun, 30 Jun 2002 15:34:10 +0000 [thread overview]
Message-ID: <marc-lartc-102545134107629@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102536735802327@msgid-missing>
> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
> Behalf Of bert hubert
> Sent: Saturday, June 29, 2002 6:13 PM
> To: Vik Heyndrickx
> Cc: lartc@mailman.ds9a.nl
> Subject: [LARTC] Re: priomap table
>
> > Now, why are this "band column" and priomap list different? Is there a
> > relationship between them, or is it just a mistake, or did I
> miss something
> > (also a good possibility)?
>
> There is an additional level of indirection in there I think. I really
> really went over this with a fine comb when I wrote it. Perhaps something
> changed? Would the commandline default priomap make sense?
The default priomap doesn't make sense if put as-is in the last column.
Anyway, the default priomap with a current kernel is still the same as in
the documentation and it appears that "Minimize Delay" pings are indeed put
into prio/pfifo_fast band 0, just like the table suggested. The extra layer
of indirection is the fourth column of the table, which originates from I
don't know where.
I was experimenting with a four band prio qdisc. Now that I understand this,
I think I've got to go back to the drawing board. I wondered why my
"Minimize Delay" pings were classified into the second band qdisc.
--
Vik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-30 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 16:12 [LARTC] Re: priomap table bert hubert
2002-06-30 15:34 ` Vik Heyndrickx [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-102545134107629@msgid-missing \
--to=vik.heyndrickx@pandora.be \
--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.