From: John Fastabend <john.fastabend@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
xiyou.wangcong@gmail.com, jhs@mojatatu.com,
netdev@vger.kernel.org, paulmck@linux.vnet.ibm.com,
brouer@redhat.com
Subject: Re: [net-next PATCH v5 00/16] net/sched rcu filters
Date: Fri, 12 Sep 2014 20:12:58 -0700 [thread overview]
Message-ID: <5413B63A.4040806@gmail.com> (raw)
In-Reply-To: <1410576591.7106.128.camel@edumazet-glaptop2.roam.corp.google.com>
On 09/12/2014 07:49 PM, Eric Dumazet wrote:
> On Fri, 2014-09-12 at 22:36 -0400, David Miller wrote:
>> John you're getting really close with this series.
>>
>> Why don't you post everything up to the tc actions stuff,
>> which Eric has ACK'd already, and I can put that all into
>> the net-next tree right now.
>>
>> Then you can concentrate on the bits that remain without
>> having to post the other stuff over and over again.
>
>
> +2 ;)
>
>
>
Great. First round of 12 patches on the way.
Thanks for all the feedback/comments Eric.
--
John Fastabend Intel Corporation
prev parent reply other threads:[~2014-09-13 3:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 16:28 [net-next PATCH v5 00/16] net/sched rcu filters John Fastabend
2014-09-12 16:28 ` [net-next PATCH v5 01/16] net: qdisc: use rcu prefix and silence sparse warnings John Fastabend
2014-09-12 16:36 ` Eric Dumazet
2014-09-12 16:29 ` [net-next PATCH v5 02/16] net: rcu-ify tcf_proto John Fastabend
2014-09-12 16:40 ` Eric Dumazet
2014-09-12 16:29 ` [net-next PATCH v5 03/16] net: sched: cls_basic use RCU John Fastabend
2014-09-12 16:30 ` [net-next PATCH v5 04/16] net: sched: cls_cgroup " John Fastabend
2014-09-12 16:30 ` [net-next PATCH v5 05/16] net: sched: cls_flow " John Fastabend
2014-09-12 16:31 ` [net-next PATCH v5 06/16] net: sched: fw " John Fastabend
2014-09-12 16:31 ` [net-next PATCH v5 07/16] net: sched: RCU cls_route John Fastabend
2014-09-12 16:31 ` [net-next PATCH v5 08/16] net: sched: RCU cls_tcindex John Fastabend
2014-09-12 16:32 ` [net-next PATCH v5 09/16] net: sched: make cls_u32 per cpu John Fastabend
2014-09-12 16:32 ` [net-next PATCH v5 10/16] net: sched: make cls_u32 lockless John Fastabend
2014-09-12 16:33 ` [net-next PATCH v5 11/16] net: sched: rcu'ify cls_rsvp John Fastabend
2014-09-12 18:21 ` Eric Dumazet
2014-09-12 16:33 ` [net-next PATCH v5 12/16] net: sched: rcu'ify cls_bpf John Fastabend
2014-09-12 18:22 ` Eric Dumazet
2014-09-12 16:34 ` [net-next PATCH v5 13/16] net: sched: make tc_action safe to walk under RCU John Fastabend
2014-09-12 20:51 ` Eric Dumazet
2014-09-13 0:05 ` John Fastabend
2014-09-12 16:34 ` [net-next PATCH v5 14/16] net: sched: make bstats per cpu and estimator RCU safe John Fastabend
2014-09-12 23:49 ` Eric Dumazet
2014-09-12 16:34 ` [net-next PATCH v5 15/16] net: sched: make qstats per cpu John Fastabend
2014-09-12 23:55 ` Eric Dumazet
2014-09-12 16:35 ` [net-next PATCH v5 16/16] net: sched: drop ingress qdisc lock John Fastabend
2014-09-12 23:56 ` Eric Dumazet
2014-09-13 1:33 ` Eric Dumazet
2014-09-13 2:36 ` [net-next PATCH v5 00/16] net/sched rcu filters David Miller
2014-09-13 2:49 ` Eric Dumazet
2014-09-13 3:12 ` John Fastabend [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=5413B63A.4040806@gmail.com \
--to=john.fastabend@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.