From: Jesper Juhl <jesper.juhl@gmail.com>
To: zhang yuanyi <zhangyuanyi@gmail.com>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>, linux-kernel@vger.kernel.org
Subject: Re: What about adding range support for u32 classifier?
Date: Tue, 30 Aug 2005 14:14:30 +0200 [thread overview]
Message-ID: <9a8748490508300514414410b5@mail.gmail.com> (raw)
In-Reply-To: <21c563b6050829202372189527@mail.gmail.com>
On 8/30/05, zhang yuanyi <zhangyuanyi@gmail.com> wrote:
> Hello, everyone!
>
> The "range support" may be puzzled, but I don't know how to express my
> problem exactly because of my poor english.
>
> Just take an example, I may need all udp packets received on eth0
> which source port is greater than 53 going into flow 10:1, and I only
> wanna to type one tc command like this(In fact, I communicated with
> kernel directly):
>
> tc filter add dev eth0 parent ffff: protocol ip prio 20 \
> u32 match udp sport gt 53 0xffff \
> match ip protocol 17 0xff\
> flowid 10:1
>
> But I found I can't, because u32 classifier doesn't support matching
> multi-value in one key.So I need to add (65535-53) keys to a u32
> filter to implement this.
>
> I intend to solve this problem by modifying u32 filter to match
> multi-value in one key, but I am worrying the preformance.
>
> Can someone give me some suggestions?
>
How is this a kernel problem?
"tc" is a userspace app. I think you'd be better off talking to Alexey
Kuznetsov (added to Cc), who wrote tc, about this.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-08-30 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 3:23 What about adding range support for u32 classifier? zhang yuanyi
2005-08-30 12:14 ` Jesper Juhl [this message]
2005-09-01 7:26 ` zhang yuanyi
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=9a8748490508300514414410b5@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangyuanyi@gmail.com \
/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.