From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Li Zefan <lizefan@huawei.com>, Eric Dumazet <edumazet@google.com>,
<pshelar@nicira.com>, <jasowang@redhat.com>,
Simon Horman <horms@verge.net.au>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
<cgroups@vger.kernel.org>,
<containers@lists.linux-foundation.org>,
Patrick McHardy <kaber@trash.net>, <xemul@openvz.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 0/4] net_cls for sys container
Date: Mon, 6 Jan 2014 15:54:53 +0800 [thread overview]
Message-ID: <52CA614D.6040702@huawei.com> (raw)
In-Reply-To: <CAM_iQpW0+Ftvk=QBE+0yMNW00VkBee1+yAEmbPkT+zjij9RX-Q@mail.gmail.com>
On 2014/1/3 13:20, Cong Wang wrote:
> On Thu, Jan 2, 2014 at 7:11 PM, Libo Chen <clbchenlibo.chen@huawei.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
>
> .
>
next prev parent reply other threads:[~2014-01-06 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 3:11 [RFC PATCH net-next 0/4] net_cls for sys container Libo Chen
2014-01-03 5:20 ` Cong Wang
2014-01-06 7:54 ` Libo Chen [this message]
2014-01-06 8:42 ` Gao feng
2014-01-06 10:06 ` Libo Chen
2014-01-15 0:50 ` Eric W. Biederman
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=52CA614D.6040702@huawei.com \
--to=clbchenlibo.chen@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@verge.net.au \
--cc=jasowang@redhat.com \
--cc=jhs@mojatatu.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=serge.hallyn@ubuntu.com \
--cc=xemul@openvz.org \
--cc=xiyou.wangcong@gmail.com \
/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