Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Leonardo Balliache <leoball@opalsoft.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Question on prio qdisc
Date: Wed, 09 Jul 2003 02:58:07 +0000	[thread overview]
Message-ID: <marc-lartc-105771959028426@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105714958700490@msgid-missing>

Hi, Lars:

At 10:10 a.m. 08/07/03 +0200, you wrote:

> >
> > each queue is an independent queue. Then if high priority packets are
> > dropped is because the high priority queue has overflow, not because some
> > (unique?) queue is full from low priority packets.
>
>I am little confused.  If typed ifconfig, we can see "txqueuelen:100".
>Will this imply that all three bands hold by prio are sharing this 100
>packages capacity, or can each of these three bands each occupy 100
>packages in its buffer.  In the latter, this means prio can maximum occupy
>300 packages...
>
>This problem will also imply HTB and other schedulers..
>
>
>Regards
>
>Lars Landmark

I'm not very sure if the total queue length is 100 or 300 because I was
searching the code and I can't find any information that tell me what the
real length is.

Because "ip link" shows me that qlen is 100, I have to suppose that total
length is 100.

But anyway, PRIO queing discipline principle calls that each priority queue
is independent, then we can't have the prio 0 queue full of prio 1 or 2
packets (being the filters working well). It goes against the PRIO queuing
discipline principle.

In "Differentiated Service on Linux HOWTO" (work in progress) I present
a PRIO queuing discipline explanation using some documentation taken
from Juniper Networks. Have a look at http://opalsoft.net/qos.

Also if you read about Cisco PQ the principle is identical. If we don't
respect the principle, then the queue can be any sort of queue, but
certainly, not a PRIO queue. Then it´s not posible to ask on PRIO for something
that drops an already enqueue packet to make run for a new arriving one.

I suggest that configurations and tests made to reach that conclusions were 
revised.

Best regards,

Leonardo Balliache





_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-07-09  2:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 12:36 [LARTC] Question on prio qdisc Cain, Joseph
2003-07-02 16:28 ` Cheng Kwok Wing, William
2003-07-02 16:42 ` Lars Landmark
2003-07-02 19:29 ` Cain, Joseph
2003-07-07 18:08 ` Leonardo Balliache
2003-07-08 19:31 ` Cain, Joseph
2003-07-09  2:58 ` Leonardo Balliache [this message]
2003-07-09  3:35 ` Leonardo Balliache

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-105771959028426@msgid-missing \
    --to=leoball@opalsoft.net \
    --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