[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130523011137.GB26193@verge.net.au>
Date: Thu, 23 May 2013 10:11:37 +0900
From: Simon Horman <horms@...ge.net.au>
To: Peter Zijlstra <peterz@...radead.org>
Cc: David Miller <davem@...emloft.net>, eric.dumazet@...il.com,
ja@....bg, mingo@...hat.com, paulmck@...ux.vnet.ibm.com,
lvs-devel@...r.kernel.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org, linux-kernel@...r.kernel.org,
pablo@...filter.org, dipankar@...ibm.com
Subject: Re: [PATCH ipvs-next v3 0/2] sched: Add cond_resched_rcu_lock()
helper
On Wed, May 22, 2013 at 11:00:51AM +0200, Peter Zijlstra wrote:
> On Wed, May 22, 2013 at 01:31:08AM -0700, David Miller wrote:
> > From: Peter Zijlstra <peterz@...radead.org>
> > Date: Wed, 22 May 2013 09:54:38 +0200
> >
> > > On Wed, May 22, 2013 at 02:50:30PM +0900, Simon Horman wrote:
> > >> Add a helper that for use in loops which read data protected by RCU and
> > >> may have a large number of iterations. Such an example is dumping the list
> > >> of connections known to IPVS: ip_vs_conn_array() and ip_vs_conn_seq_next().
> > >>
> > >> This series also updates IPVS to use the helper.
> > >>
> > >> Simon Horman (2):
> > >> sched: add cond_resched_rcu() helper
> > >> ipvs: use cond_resched_rcu() helper when walking connections
> > >>
> > >> include/linux/sched.h | 9 +++++++++
> > >> net/netfilter/ipvs/ip_vs_conn.c | 23 ++++++++---------------
> > >> 2 files changed, 17 insertions(+), 15 deletions(-)
> > >
> > > Acked-by: Peter Zijlstra <peterz@...radead.org>
> > >
> > > How do you want to go about merging this? Do you want to route it
> > > through the net tree or through -tip?
> >
> > I think we can have Pablo merge it into his netfilter tree.
>
> Works for me. Thanks!
Thanks, I will queue it up in ipvs-next and pass it to Pablo from there.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists