netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Corey Hickey <bugfood-ml@fatooh.org>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [NET_SCHED 00/04]: External SFQ classifiers/flow classifier
Date: Tue, 01 Apr 2008 20:04:56 +0100	[thread overview]
Message-ID: <47F28758.1010401@andyfurniss.entadsl.com> (raw)
In-Reply-To: <47F22CF5.4080806@trash.net>

Patrick McHardy wrote:
> Andy Furniss wrote:
>> Patrick McHardy wrote:
>>
>>> tc filter add dev eth0 protocol ip pref 1 parent 1: handle 1 \
>>>         flow hash keys dst divisor 1024
>>>
>>
>> I've been trying to incorporate this into my own setup but haven't got 
>> very far :-)
>>
>> I don't even know if it's possible to attach to htb subclasses and 
>> expect it to work. If it is do you have an example (is this what 
>> baseclass is for?).
>>
>> I can attach to a filter to other than parent 1:0 OK but it doesn't do 
>> anything.
>>
>> I have also tried incorporating flow into the 1:0 filters that filter 
>> to the htb subclasses that have the sfqs attached to them, but can't 
>> get ematch to work - but then I have never been able to get ematch to 
>> work. I can't find any examples. All I need if this is the way to go 
>> is to match on mark and match on anything.
>>
>> Is this possible and if so, do you have/know of any examples?
> 
> What exactly are you trying to do? If you attach the classifier
> to HTB, it will classify to HTB classes. I guess you actually
> want to use it for SFQ, which should work with:
> 
> tc qdisc add ... handle x: sfq
> tc filter add parent x: protocol all flow ...
> 

Ahh thanks. It's so obvious now :-)

I didn't have handles specified on the sfqs and was trying to use the 
htb leafs handles.

It's cool being able to see the sfq flows.

Andy.



  reply	other threads:[~2008-04-01 19:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 17:58 [NET_SCHED 00/04]: External SFQ classifiers/flow classifier Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 01/04]: Constify struct tcf_ext_map Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 02/04]: sch_sfq: add support for external classifiers Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 03/04]: sch_sfq: make internal queues visible as classes Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 04/04]: Add flow classifier Patrick McHardy
2008-02-01  2:37 ` [NET_SCHED 00/04]: External SFQ classifiers/flow classifier David Miller
2008-02-02 23:23 ` Corey Hickey
2008-02-04 17:48   ` Patrick McHardy
2008-02-04 18:25     ` Corey Hickey
2008-03-29 23:35     ` Andy Furniss
2008-04-01 12:39       ` Patrick McHardy
2008-04-01 19:04         ` Andy Furniss [this message]
2008-04-02 11:42           ` Andy Furniss
2008-04-02 12:37             ` Patrick McHardy
2008-04-02 16:26               ` Andy Furniss
2008-04-04 10:42                 ` Andy Furniss
2008-04-04 10:45                   ` Patrick McHardy
2008-04-04 17:01                     ` Andy Furniss
2008-04-04 18:54                       ` Andy Furniss
2008-04-07 13:43                         ` Andy Furniss
2008-04-07 13:44                           ` Patrick McHardy
2008-04-07 15:14                             ` Andy Furniss

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=47F28758.1010401@andyfurniss.entadsl.com \
    --to=lists@andyfurniss.entadsl.com \
    --cc=bugfood-ml@fatooh.org \
    --cc=kaber@trash.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).