Netdev List
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: davem@davemloft.net
Cc: xiyou.wangcong@gmail.com, jiri@resnulli.us,
	netdev@vger.kernel.org, viro@zeniv.linux.org.uk,
	Jamal Hadi Salim <hadi@mojatatu.com>
Subject: [PATCH net-next v2 00/12] net: sched: cls_u32 Various improvements
Date: Mon,  8 Oct 2018 06:22:32 -0400	[thread overview]
Message-ID: <20181008102244.22212-1-jhs@emojatatu.com> (raw)

From: Jamal Hadi Salim <hadi@mojatatu.com>

Various improvements from Al.

Changes from version 1: Add missing commit 

Al Viro (11):
  net: sched: cls_u32: mark root hnode explicitly
  net: sched: cls_u32: disallow linking to root hnode
  net: sched: cls_u32: make sure that divisor is a power of 2
  net: sched: cls_u32: get rid of unused argument of u32_destroy_key()
  net: sched: cls_u32: get rid of tc_u_knode ->tp
  net: sched: cls_u32: get rid of tc_u_common ->rcu
  net: sched: cls_u32: clean tc_u_common hashtable
  net: sched: cls_u32: pass tc_u_common to u32_set_parms() instead of
    tc_u_hnode
  net: sched: cls_u32: the tp_c argument of u32_set_parms() is always
    tp->data
  net: sched: cls_u32: get rid of tp_c
  net: sched: cls_u32: keep track of knodes count in tc_u_common
  net: sched: cls_u32: simplify the hell out u32_delete() emptiness
    check

 net/sched/cls_u32.c | 121 +++++++++++++++++-----------------------------------
 1 file changed, 38 insertions(+), 83 deletions(-)

-- 
2.11.0

             reply	other threads:[~2018-10-08 17:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 10:22 Jamal Hadi Salim [this message]
2018-10-08 10:22 ` [PATCH net-next v2 01/12] net: sched: cls_u32: mark root hnode explicitly Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 02/12] net: sched: cls_u32: disallow linking to root hnode Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 03/12] net: sched: cls_u32: make sure that divisor is a power of 2 Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 04/12] net: sched: cls_u32: get rid of unused argument of u32_destroy_key() Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 05/12] net: sched: cls_u32: get rid of tc_u_knode ->tp Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 06/12] net: sched: cls_u32: get rid of tc_u_common ->rcu Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 07/12] net: sched: cls_u32: clean tc_u_common hashtable Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 08/12] net: sched: cls_u32: pass tc_u_common to u32_set_parms() instead of tc_u_hnode Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 09/12] net: sched: cls_u32: the tp_c argument of u32_set_parms() is always tp->data Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 10/12] net: sched: cls_u32: get rid of tp_c Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 11/12] net: sched: cls_u32: keep track of knodes count in tc_u_common Jamal Hadi Salim
2018-10-08 10:22 ` [PATCH net-next v2 12/12] net: sched: cls_u32: simplify the hell out u32_delete() emptiness check Jamal Hadi Salim
2018-10-08 17:33 ` [PATCH net-next v2 00/12] net: sched: cls_u32 Various improvements David Miller

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=20181008102244.22212-1-jhs@emojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=hadi@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --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