netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Badalian Vyacheslav <slavon@bigtelecom.ru>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: tc filter flow hash question
Date: Tue, 30 Jun 2009 08:57:06 +0000	[thread overview]
Message-ID: <20090630085706.GD5589@ff.dom.local> (raw)
In-Reply-To: <4A49C906.9010102@bigtelecom.ru>

On 30-06-2009 10:12, Badalian Vyacheslav wrote:
> Hello all.
> Sorry for mail to this maillist, but in internet i can't found any
> information to understand this situation, lartc list is dead, function
> do not documented and only developers understand how it works.

They only pretend they understand how it works...

> 
> As i understand if i add flow hash i divide speed to KEYs (example to
> dst) not for sessions right?
> 
> Why if i add simple example my traffic stop and i get DROP at parent class?
> 
> This my sample
> 
> tc qdisc add dev eth0 root handle 1 htb default 7
> class add dev eth0 parent 1: classid 1:7 htb rate 500mbit ceil 1000mbit
> prio 3
> qdisc add dev eth0 parent 1:7 handle 10: sfq perturb 10
> # all normal
> tc filter add dev eth0 protocol ip parent 10: handle 2 flow hash keys
> src,dst
> # all traffic drop
> 

Here are some hints (if we don't mention google ;-)
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.29.y.git;a=commitdiff;h=e5dfb815181fcb186d6080ac3a091eadff2d98fe

Regards,
Jarek P.

  reply	other threads:[~2009-06-30  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  8:12 tc filter flow hash question Badalian Vyacheslav
2009-06-30  8:57 ` Jarek Poplawski [this message]
2009-06-30  9:18   ` Badalian Vyacheslav
2009-06-30  9:23     ` Jarek Poplawski
2009-06-30  9:49       ` Badalian Vyacheslav
2009-06-30  9:56         ` Jarek Poplawski
2009-06-30 10:30           ` Badalian Vyacheslav
2009-06-30 11:09             ` Jarek Poplawski

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=20090630085706.GD5589@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=slavon@bigtelecom.ru \
    /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;
as well as URLs for NNTP newsgroup(s).