From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@gentwo.org>
Cc: Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] slub: Use new node functions
Date: Tue, 17 Jun 2014 14:47:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406171447010.27899@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1406131055590.913@gentwo.org>
On Fri, 13 Jun 2014, Christoph Lameter wrote:
> On Wed, 11 Jun 2014, David Rientjes wrote:
>
> > > + for_each_kmem_cache_node(s, node, n) {
> > >
> > > free_partial(s, n);
> > > if (n->nr_partial || slabs_node(s, node))
> >
> > Newline not removed?
>
> Ok got through the file and removed all the lines after
> for_each_kmem_cache_node.
>
> >
> > > @@ -3407,11 +3401,7 @@ int __kmem_cache_shrink(struct kmem_cach
> > > return -ENOMEM;
> > >
> > > flush_all(s);
> > > - for_each_node_state(node, N_NORMAL_MEMORY) {
> > > - n = get_node(s, node);
> > > -
> > > - if (!n->nr_partial)
> > > - continue;
> > > + for_each_kmem_cache_node(s, node, n) {
> > >
> > > for (i = 0; i < objects; i++)
> > > INIT_LIST_HEAD(slabs_by_inuse + i);
> >
> > Is there any reason not to keep the !n->nr_partial check to avoid taking
> > n->list_lock unnecessarily?
>
> No this was simply a mistake the check needs to be preserved.
>
>
> Subject: slub: Fix up earlier patch
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Thanks!
Acked-by: David Rientjes <rientjes@google.com>
as merged in -mm.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-06-17 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 19:15 [PATCH 0/3] slab: common kmem_cache_cpu functions V2 Christoph Lameter
2014-06-11 19:15 ` [PATCH 1/3] slab common: Add functions for kmem_cache_node access Christoph Lameter
2014-06-11 23:07 ` David Rientjes
2014-06-12 6:10 ` Joonsoo Kim
2014-06-17 21:17 ` Andrew Morton
2014-06-17 21:45 ` David Rientjes
2014-06-11 19:15 ` [PATCH 2/3] slub: Use new node functions Christoph Lameter
2014-06-11 23:12 ` David Rientjes
2014-06-13 16:02 ` Christoph Lameter
2014-06-17 21:47 ` David Rientjes [this message]
2014-06-11 19:15 ` [PATCH 3/3] slab: Use get_node() and kmem_cache_node() functions Christoph Lameter
2014-06-11 23:15 ` David Rientjes
2014-06-12 6:35 ` Joonsoo Kim
2014-06-13 16:32 ` Christoph Lameter
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=alpine.DEB.2.02.1406171447010.27899@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
/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