From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: Cong Wang <xiyou.wangcong@gmail.com>
Subject: [PATCH net-next v3 0/6] net_sched: some cleanup and improvments
Date: Thu, 12 Dec 2013 21:47:47 -0800 [thread overview]
Message-ID: <1386913673-8210-1-git-send-email-xiyou.wangcong@gmail.com> (raw)
Here are some cleanup and improvements for tc filters
and tc actions.
v2 -> v3:
* fix a typo introduced during rebase
v1 -> v2:
* fix a smatch warning and a checkpatch warning
* add a cover letter
* add a missing synchronize_rcu()
Cong Wang (6):
net_sched: remove get_stats from tc_action_ops
net_sched: act: use standard struct list_head
net_sched: mirred: remove action when the target device is gone
net_sched: cls: refactor out struct tcf_ext_map
net_sched: init struct tcf_hashinfo at register time
net_sched: convert tcf_hashinfo to hlist and use rcu
include/net/act_api.h | 41 +++++++---
include/net/pkt_cls.h | 37 +++++----
include/net/tc_act/tc_mirred.h | 4 +-
net/sched/act_api.c | 180 ++++++++++++++++++-----------------------
net/sched/act_csum.c | 13 ++-
net/sched/act_gact.c | 13 ++-
net/sched/act_ipt.c | 21 +++--
net/sched/act_mirred.c | 31 ++++---
net/sched/act_nat.c | 12 ++-
net/sched/act_pedit.c | 12 ++-
net/sched/act_police.c | 65 +++++++--------
net/sched/act_simple.c | 20 ++---
net/sched/act_skbedit.c | 13 ++-
net/sched/cls_api.c | 80 +++++++++---------
net/sched/cls_basic.c | 13 ++-
net/sched/cls_bpf.c | 13 ++-
net/sched/cls_cgroup.c | 14 ++--
net/sched/cls_flow.c | 13 ++-
net/sched/cls_fw.c | 13 ++-
net/sched/cls_route.c | 13 ++-
net/sched/cls_rsvp.h | 13 ++-
net/sched/cls_tcindex.c | 17 ++--
net/sched/cls_u32.c | 13 ++-
23 files changed, 304 insertions(+), 360 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-12-13 5:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 5:47 Cong Wang [this message]
2013-12-13 5:47 ` [PATCH net-next v3 1/6] net_sched: remove get_stats from tc_action_ops Cong Wang
2013-12-13 10:21 ` David Laight
2013-12-13 18:33 ` Cong Wang
2013-12-13 21:27 ` Jamal Hadi Salim
2013-12-13 21:34 ` Cong Wang
2013-12-13 21:40 ` Jamal Hadi Salim
2013-12-13 21:50 ` Cong Wang
2013-12-13 22:19 ` Jamal Hadi Salim
2013-12-13 23:23 ` David Miller
2013-12-14 2:59 ` Jamal Hadi Salim
2013-12-14 5:15 ` David Miller
2013-12-14 12:22 ` Jamal Hadi Salim
2013-12-15 3:26 ` David Miller
2013-12-13 23:21 ` David Miller
2013-12-13 12:05 ` Jamal Hadi Salim
2013-12-13 18:38 ` Cong Wang
2013-12-13 21:29 ` Jamal Hadi Salim
2013-12-13 5:47 ` [PATCH net-next v3 2/6] net_sched: act: use standard struct list_head Cong Wang
2013-12-13 12:08 ` Jamal Hadi Salim
2013-12-13 18:48 ` Cong Wang
2013-12-13 21:29 ` Jamal Hadi Salim
2013-12-13 21:35 ` Cong Wang
2013-12-13 5:47 ` [PATCH net-next v3 3/6] net_sched: mirred: remove action when the target device is gone Cong Wang
2013-12-13 12:07 ` Jamal Hadi Salim
2013-12-13 12:12 ` David Laight
2013-12-13 18:52 ` Cong Wang
2013-12-13 5:47 ` [PATCH net-next v3 4/6] net_sched: cls: refactor out struct tcf_ext_map Cong Wang
2013-12-13 5:47 ` [PATCH net-next v3 5/6] net_sched: init struct tcf_hashinfo at register time Cong Wang
2013-12-13 5:47 ` [PATCH net-next v3 6/6] net_sched: convert tcf_hashinfo to hlist and use rcu Cong Wang
2013-12-13 6:48 ` Eric Dumazet
2013-12-13 21:44 ` Cong Wang
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=1386913673-8210-1-git-send-email-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=netdev@vger.kernel.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).