From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, mlxsw@mellanox.com
Subject: Re: [patch net-next 0/9] net: sched: remove some tp->q usage
Date: Mon, 16 Oct 2017 21:01:00 +0100 (WEST) [thread overview]
Message-ID: <20171016.210100.1253627616514908067.davem@davemloft.net> (raw)
In-Reply-To: <20171013120105.23358-1-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Fri, 13 Oct 2017 14:00:56 +0200
> From: Jiri Pirko <jiri@mellanox.com>
>
> In order to prepare for block sharing, tcf_proto instances need to be
> independent on particular qdisc instances. This patchset takes care of
> removal of couple occurrences of tp->q usage.
Series applied, thanks Jiri.
prev parent reply other threads:[~2017-10-16 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 12:00 [patch net-next 0/9] net: sched: remove some tp->q usage Jiri Pirko
2017-10-13 12:00 ` [patch net-next 1/9] net: sched: store Qdisc pointer in struct block Jiri Pirko
2017-10-13 12:00 ` [patch net-next 2/9] net: sched: store net pointer in block and introduce qdisc_net helper Jiri Pirko
2017-10-13 12:00 ` [patch net-next 3/9] net: sched: introduce tcf_block_q and tcf_block_dev helpers Jiri Pirko
2017-10-13 12:01 ` [patch net-next 4/9] net: sched: teach tcf_bind/unbind_filter to use block->q Jiri Pirko
2017-10-13 12:01 ` [patch net-next 5/9] net: sched: ematch: obtain net pointer from blocks Jiri Pirko
2017-10-13 12:01 ` [patch net-next 6/9] net: sched: cls_u32: use block instead of q in tc_u_common Jiri Pirko
2017-10-13 12:01 ` [patch net-next 7/9] net: sched: tcindex, fw, flow: use tcf_block_q helper to get struct Qdisc Jiri Pirko
2017-10-13 12:01 ` [patch net-next 8/9] net: sched: use tcf_block_q helper to get q pointer for sch_tree_lock Jiri Pirko
2017-10-13 12:01 ` [patch net-next 9/9] net: sched: propagate q and parent from caller down to tcf_fill_node Jiri Pirko
2017-10-16 20:01 ` David Miller [this message]
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=20171016.210100.1253627616514908067.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).