[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090617094907.e8cd77bd.usui@mxm.nes.nec.co.jp>
Date: Wed, 17 Jun 2009 09:49:07 +0900
From: Minoru Usui <usui@....nes.nec.co.jp>
To: Thomas Graf <tgraf@...radead.org>
Cc: Paul Menage <menage@...gle.com>,
David Miller <davem@...emloft.net>, tgraf@...g.ch,
netdev@...r.kernel.org, containers@...ts.linux-foundation.org,
hadi@...erus.ca, jarkao2@...il.com
Subject: Re: [Devel] Re: [PATCH 1/1] cls_cgroup: unify classid syntax to tc
On Mon, 15 Jun 2009 06:19:19 -0400
Thomas Graf <tgraf@...radead.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.
--
Minoru Usui <usui@....nes.nec.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists