From: "Ranjit Manomohan" <ranjitm@google.com>
To: "Patrick McHardy" <kaber@trash.net>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lizf@cn.fujitsu.com, menage@google.com
Subject: Re: [PATCH] Traffic control cgroups subsystem
Date: Wed, 23 Jul 2008 16:54:03 -0700 [thread overview]
Message-ID: <166fe7950807231654ib5759e1kae54887f0918d3fb@mail.gmail.com> (raw)
In-Reply-To: <4887B1F0.3000407@trash.net>
On Wed, Jul 23, 2008 at 3:34 PM, Patrick McHardy <kaber@trash.net> wrote:
> Andrew Morton wrote:
>>
>> On Tue, 22 Jul 2008 10:44:18 -0700 (PDT)
>> Ranjit Manomohan <ranjitm@google.com> wrote:
>>
>>> @@ -359,7 +370,12 @@ static int flow_classify(struct sk_buff *skb, struct
>>> tcf_proto *tp,
>>> classid %= f->divisor;
>>>
>>> res->class = 0;
>>> - res->classid = TC_H_MAKE(f->baseclass, f->baseclass +
>>> classid);
>>> +
>>> + if (key == FLOW_KEY_CGROUP_CLASSID)
>>> + res->classid = TC_H_MAKE(f->baseclass, classid);
>>> + else
>>> + res->classid = TC_H_MAKE(f->baseclass,
>>> + f->baseclass + classid);
>>
>> This causes a warning:
>>
>> net/sched/cls_flow.c: In function 'flow_classify':
>> net/sched/cls_flow.c:344: warning: 'key' may be used uninitialized in this
>> function
>>
>> that warning is a non-issue if we happen to know that f->nkeys can
>> never be zero. I don't know if that is guaranteed at this code site?
>
> It is by the flow_change() function, but special casing the
> CGROUP_CLASSID is not acceptable anyway. There should be no
> need for that, a simple linear mapping to classids is done
> by default in mapping mode, the sk_cgroup_classid simply
> shouldn't include qdisc IDs.
I did not want to special case it but I want an identity mapping not a
linear one. For some reason a baseclass of X:0 is not allowed, and
there does not seem to be a clean way to get a 1-1 mapping (tc.classid
-> X:tc.classid). I would have to workaround it by using a baseclass
of the form X:Y and then subtracting Y from the value written to
tc.classid which seemed very non intuitive.
Any particular reason for this restriction? Am I missing any other
technique of getting a 1-1 mapping using the flow classifier?
-Thanks,
Ranjit
>
next prev parent reply other threads:[~2008-07-23 23:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 17:44 Ranjit Manomohan
2008-07-23 22:05 ` Andrew Morton
2008-07-23 22:34 ` Patrick McHardy
2008-07-23 23:54 ` Ranjit Manomohan [this message]
2008-07-24 0:17 ` Patrick McHardy
2008-07-24 23:45 ` Thomas Graf
2008-07-25 1:16 ` Ranjit Manomohan
2008-07-25 9:29 ` Thomas Graf
2008-07-25 1:18 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2008-07-22 4:08 Ranjit Manomohan
2008-07-22 10:35 ` Patrick McHardy
2008-07-22 12:14 ` Paul Menage
2008-07-22 12:48 ` Patrick McHardy
2008-07-22 12:56 ` Paul Menage
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=166fe7950807231654ib5759e1kae54887f0918d3fb@mail.gmail.com \
--to=ranjitm@google.com \
--cc=akpm@linux-foundation.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--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
Powered by JetHome