All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radoslaw Horodniczy" <rh@cxt.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] prio, kernel 2.6: patch?
Date: Tue, 28 Mar 2006 09:47:51 +0000	[thread overview]
Message-ID: <025a01c6524c$ae642a70$08020a0a@HT003> (raw)
In-Reply-To: <49734.192.168.10.150.1143535491.squirrel@mail.duet.it>



> hi to all,
> I'm sorry, the previous mail was incomplete. I rewrite all COMPLETE
> informations.
>
> I'm studying traffic shaping using kernel 2.6.8 (debian sarge).
>
> well, I have this problem: priority doesn't work.
> I try with:
> - qdisc prio:
>     tc qdisc add dev eth1 root handle 12: prio bands 3
>     tc qdisc add dev eth1 parent 12:1 handle 13: tbf rate 10Mbit \
>              buffer 1600 limit 3000
>     tc qdisc add dev eth1 parent 12:2 handle 14: tbf rate 10Mbit \
>              buffer 1600 limit 3000
>     tc qdisc add dev eth1 parent 12:3 handle 15: tbf rate 10Mbit \
>              buffer 1600 limit 3000
>
>     tc filter add dev eth1 protocol ip handle $MARK1 fw flowid 12:1
>     tc filter add dev eth1 protocol ip handle $MARK2 fw flowid 12:2
>     tc filter add dev eth1 protocol ip handle $MARK3 fw flowid 12:3

Yes there is a bug with PRIO, as I know from kernel 2.6.12 there is no this 
bug.
Try to find patch for file cls_u32.c or install new kernel

Regards

Radek 

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-03-28  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  8:44 [LARTC] prio, kernel 2.6: patch? Fabio
2006-03-28  9:05 ` Fabio
2006-03-28  9:47 ` Radoslaw Horodniczy [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='025a01c6524c$ae642a70$08020a0a@HT003' \
    --to=rh@cxt.pl \
    --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.