From: Libo Chen <clbchenlibo.chen@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: edumazet@google.com, jasowang@redhat.com, horms@verge.net.au,
Serge Hallyn <serge.hallyn@ubuntu.com>,
netdev@vger.kernel.org, cgroups@vger.kernel.org,
containers@lists.linux-foundation.org, kaber@trash.net,
xemul@openvz.org, ebiederm@xmission.com,
LKML <linux-kernel@vger.kernel.org>,
jhs@mojatatu.com, Li Zefan <lizefan@huawei.com>
Subject: [RFC PATCH net-next 1/4] net: introduce backup_classid to struct skbuff
Date: Fri, 3 Jan 2014 11:11:04 +0800 [thread overview]
Message-ID: <52C62A48.1050604@huawei.com> (raw)
introduce backup_classid to struct skbuff,
we can use it to backup sk_classid when net_ns switch.
Signed-off-by: Libo Chen <clbchenlibo.chen@huawei.com>
---
include/linux/skbuff.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index c5cd016..b76e871 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -492,6 +492,9 @@ struct sk_buff {
#ifdef CONFIG_NET_CLS_ACT
__u16 tc_verd; /* traffic control verdict */
#endif
+#ifdef CONFIG_NET_CLS_CGROUP
+ __u32 backup_classid;
+#endif
#endif
__u16 queue_mapping;
--
1.8.2.2
next reply other threads:[~2014-01-03 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 3:11 Libo Chen [this message]
[not found] ` <52C62A48.1050604-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-01-03 5:34 ` [RFC PATCH net-next 1/4] net: introduce backup_classid to struct skbuff David Miller
[not found] ` <20140103.003404.1439874071277993396.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2014-01-03 6:21 ` John Fastabend
[not found] ` <52C656F2.8060803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-06 8:16 ` Libo Chen
2014-01-07 12:54 ` Libo Chen
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=52C62A48.1050604@huawei.com \
--to=clbchenlibo.chen@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--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=serge.hallyn@ubuntu.com \
--cc=xemul@openvz.org \
/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).