[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52CA614D.6040702@huawei.com>
Date: Mon, 6 Jan 2014 15:54:53 +0800
From: Libo Chen <clbchenlibo.chen@...wei.com>
To: Cong Wang <xiyou.wangcong@...il.com>
CC: David Miller <davem@...emloft.net>,
Jamal Hadi Salim <jhs@...atatu.com>,
Li Zefan <lizefan@...wei.com>,
Eric Dumazet <edumazet@...gle.com>, <pshelar@...ira.com>,
<jasowang@...hat.com>, Simon Horman <horms@...ge.net.au>,
Serge Hallyn <serge.hallyn@...ntu.com>,
"Linux Kernel Network Developers" <netdev@...r.kernel.org>,
<cgroups@...r.kernel.org>, <containers@...ts.linux-foundation.org>,
Patrick McHardy <kaber@...sh.net>, <xemul@...nvz.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH net-next 0/4] net_cls for sys container
On 2014/1/3 13:20, Cong Wang wrote:
> On Thu, Jan 2, 2014 at 7:11 PM, Libo Chen <clbchenlibo.chen@...wei.com> wrote:
>> Hi guys,
>>
>> Now, lxc created with veth can not be under control by
>> cls_cgroup.
>>
>> the former discussion:
>> http://lkml.indiana.edu/hypermail/linux/kernel/1312.1/00214.html
>>
>> In short, because cls_cgroup relys classid attached to sock
>> filter skb, but sock will be cleared inside dev_forward_skb()
>> in veth_xmit().
>
>
> So what are you trying to achieve here?
sys container using veth can be controlled by cls_cgroup basing on physic network interface
thanks,
Libo
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists