From: Li Zefan <lizf@cn.fujitsu.com>
To: Minoru Usui <usui@mxm.nes.nec.co.jp>
Cc: Thomas Graf <tgraf@infradead.org>,
netdev@vger.kernel.org, containers@lists.linux-foundation.org,
hadi@cyberus.ca, tgraf@suug.ch, Paul Menage <menage@google.com>,
David Miller <davem@davemloft.net>,
jarkao2@gmail.com
Subject: Re: [Devel] Re: [PATCH 1/1] cls_cgroup: unify classid syntax to tc
Date: Thu, 18 Jun 2009 10:01:27 +0800 [thread overview]
Message-ID: <4A399FF7.5060209@cn.fujitsu.com> (raw)
In-Reply-To: <20090617094907.e8cd77bd.usui@mxm.nes.nec.co.jp>
Minoru Usui wrote:
> On Mon, 15 Jun 2009 06:19:19 -0400
> Thomas Graf <tgraf@infradead.org> wrote:
>
>> On Mon, Jun 15, 2009 at 12:00:35PM +0900, Minoru Usui wrote:
>>> Actually, In tc <-> kernel I/F (which uses netlink), tc sets classid to hexadecimal style not X:Y style.
>>> X:Y style is result of translating by tc command.
>>>
>>> I thought this patch was very useful at first, but it's not necessary to implementing to the kernel.
>>> This function can be implemented on user space if we need.
>>> And we can also keep compatibility of net_cls.classid I/F. :-)
>>>
>>> I drop this patch. I'm sorry for confusing a lot of people.
>> I found this patch to be extremely useful if it wasn't to break
>> compatibility but that issue can be resolved by accepting both
>> formats easly.
>
> Thank you for agreeing my patch.
>
> I think you said write format only. Am I right?
> What do you think about read format?
> Do you think you should keep read format as current implementation?
>
> I think we should need to unify read/write format, if we make cls_cgroup is more userfriendly.
> Because some of people are confused about having to read their write value as different format.
> (Unfortunately, current implementation is so...)
>
> But this approach breaks compatibility, so I drop this patch.
How about adding a new control file net_cls.tc_classid?
next prev parent reply other threads:[~2009-06-18 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:05 [PATCH 1/1] cls_cgroup: unify classid syntax to tc Minoru Usui
2009-06-11 9:13 ` David Miller
2009-06-12 3:40 ` Minoru Usui
2009-06-12 4:36 ` David Miller
2009-06-12 5:06 ` [Devel] " Paul Menage
[not found] ` <6599ad830906112206n745fb0dw19cdb75d7c40b2a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-15 3:00 ` Minoru Usui
2009-06-15 10:19 ` Thomas Graf
2009-06-17 0:49 ` Minoru Usui
2009-06-18 2:01 ` Li Zefan [this message]
2009-06-18 6:15 ` Minoru Usui
2009-06-18 15:21 ` Paul Menage
2009-06-11 9:31 ` Thomas Graf
2009-06-12 1:02 ` Minoru Usui
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=4A399FF7.5060209@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=jarkao2@gmail.com \
--cc=menage@google.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@infradead.org \
--cc=tgraf@suug.ch \
--cc=usui@mxm.nes.nec.co.jp \
/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).