All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Vladychevski <niko@netspace.com.mx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] PRIOMAP, SPLIT, DEFMAP usage info + PRIO, TBF and other bugs
Date: Mon, 02 Jul 2001 22:09:22 +0000	[thread overview]
Message-ID: <marc-lartc-99411167129882@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99386571628755@msgid-missing>

> ness wrote:


> Oh, one more notice:
>     AS FAR I UNDERSTAND PRIO NOT WORKING AT ALL, OR AT LEAST
>     NOT WORKING AS IT MUST WORK.
>     First of all it not implement class manipulation functions, so if
> you just try
>     to list PRIO classes (tc class ls dev eth0) this will give you
> segmentation
>     fault :(. The more the better. I far as I understand PRIO qdisc
> creates classes
>     "on fly", so I tryed to filter some packets to this classed. After
> 2 weaks of

the advanced networking howto
(http://qos.ittc.ukans.edu/howto/node17.html) says PRIO does not support
clasess:

"Not all queuing disciplines support classes. The ones that support
classes include the CBQ, the DS_MARK, the CSZ and
the p-FIFO queuing disciplines. The rest of the queuing disciplines do
not support classes. "

but the code net/sched/sch_prio.c has prio_classify() call .... I think
the howto is too old, PRIO supports classes .....

>     experements I understand that it don't prioritize packets AT ALL.
> (I'll be glad
>     to hear that I'm wrong...)
> 

does not in my tests, I am also looking why ....


Nikolai

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

  reply	other threads:[~2001-07-02 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-30  1:45 [LARTC] PRIOMAP, SPLIT, DEFMAP usage info + PRIO, TBF and other bugs ness
2001-07-02 22:09 ` Nikolai Vladychevski [this message]
2001-07-02 22:58 ` Ivan Lopez
2001-07-02 23:41 ` Nikolai Vladychevski
2001-07-03 16:40 ` Nikolai Vladychevski

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-99411167129882@msgid-missing \
    --to=niko@netspace.com.mx \
    --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.