Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753606AbaAFKHa (ORCPT ); Mon, 6 Jan 2014 05:07:30 -0500 Received: from szxga03-in.huawei.com ([119.145.14.66]:52903 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751782AbaAFKH2 (ORCPT ); Mon, 6 Jan 2014 05:07:28 -0500 Message-ID: <52CA8026.4010106@huawei.com> Date: Mon, 6 Jan 2014 18:06:30 +0800 From: Libo Chen User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Gao feng , Cong Wang CC: David Miller , Jamal Hadi Salim , Li Zefan , Eric Dumazet , , , Simon Horman , Serge Hallyn , "Linux Kernel Network Developers" , , , Patrick McHardy , , LKML Subject: Re: [RFC PATCH net-next 0/4] net_cls for sys container References: <52C62A44.4070304@huawei.com> <52CA614D.6040702@huawei.com> <52CA6C80.9060002@cn.fujitsu.com> In-Reply-To: <52CA6C80.9060002@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.22.241] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org yes On 2014/1/6 16:42, Gao feng wrote: > On 01/06/2014 03:54 PM, Libo Chen wrote: >> On 2014/1/3 13:20, Cong Wang wrote: >>> On Thu, Jan 2, 2014 at 7:11 PM, Libo Chen 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 >> > > It's a problem about virtual nic, not container/net namespace. yes > > If veth device is running in host. the skb is transmitted firstly by veth device and then delivered > by physical device. if you set both qdisc rule on veth and physical device. which qdisc rule will take > effect? both, the end result depends on a smaller. > > In your patch, both qdisc rule are effective. it looks strange. > qdisc is based nic, does not distinguish virtual or physics. if you are all set, it means that what you want. so the logic is not the problemI and this appears to be normal. thanks, Libo > . > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/