[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120730153806.GA29697@kroah.com>
Date: Mon, 30 Jul 2012 08:38:06 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Herton Ronaldo Krzesinski <herton.krzesinski@...onical.com>
Cc: Mel Gorman <mgorman@...e.de>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
Miao Xie <miaox@...fujitsu.com>,
David Rientjes <rientjes@...gle.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Christoph Lameter <cl@...ux.com>
Subject: Re: [ 39/40] cpuset: mm: reduce large amounts of memory barrier
related damage v3
On Mon, Jul 30, 2012 at 08:37:31AM -0700, Greg Kroah-Hartman wrote:
> On Sat, Jul 28, 2012 at 02:02:31AM -0300, Herton Ronaldo Krzesinski wrote:
> > Thanks. I saw what seems another issue now on the patch too, sorry for
> > not noticing earlier: this backport is lacking the
> > write_seqcount_{begin,end} on set_mems_allowed for the case with
> > CONFIG_CPUSETS, like in the original patch:
> >
> > static inline void set_mems_allowed(nodemask_t nodemask)
> > {
> > task_lock(current);
> > + write_seqcount_begin(¤t->mems_allowed_seq);
> > current->mems_allowed = nodemask;
> > + write_seqcount_end(¤t->mems_allowed_seq);
> > task_unlock(current);
> > }
> >
>
> Ok, but that's not in a patch format that I can apply :(
>
> Care to redo it so I can add it to the existing patch?
Oh nevermind, Mel already did it.
Time for more coffee...
greg k-h
--
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