From: "George Spelvin" <linux@horizon.com>
To: cl@linux.com, rientjes@google.com
Cc: iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux@horizon.com
Subject: Re: [PATCH v2 03/10] slab: move up code to get kmem_cache_node in free_block()
Date: 8 May 2014 15:24:05 -0400 [thread overview]
Message-ID: <20140508192405.30677.qmail@ns.horizon.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1405080850420.22626@gentwo.org>
>>> @@ -3362,17 +3359,12 @@ static void free_block(struct kmem_cache *cachep, void **objpp, int nr_objects,
>>> int node)
>>> {
>>> int i;
>>> - struct kmem_cache_node *n;
>>> + struct kmem_cache_node *n = cachep->node[node];
>>>
>>> for (i = 0; i < nr_objects; i++) {
>>> - void *objp;
>>> - struct page *page;
>>> -
>>> - clear_obj_pfmemalloc(&objpp[i]);
>>> - objp = objpp[i];
>>> + void *objp = clear_obj_pfmemalloc(&objpp[i]);
>>> + struct page *page = virt_to_head_page(objp);
>>>
>>> - page = virt_to_head_page(objp);
>>> - n = cachep->node[node];
>>> list_del(&page->lru);
>>> check_spinlock_acquired_node(cachep, node);
>>> slab_put_obj(cachep, page, objp, node);
>>
>> I think this unnecessarily obfuscates the code.
> It takes the lookup out of the loop. What does the obfuscation?
Taking the lookup of n out was the original cleanup patch; that part is
not my doing.
I changed clear_obj_pfmemalloc to return the modified pointer.
(As well as storing it back in version 1 which you quoted, instead of
storing it back in version 2.)
next prev parent reply other threads:[~2014-05-08 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 21:22 [PATCH v2 03/10] slab: move up code to get kmem_cache_node in free_block() George Spelvin
2014-05-07 21:30 ` David Rientjes
2014-05-07 21:50 ` George Spelvin
2014-05-07 22:05 ` David Rientjes
2014-05-08 0:44 ` George Spelvin
2014-05-08 1:46 ` George Spelvin
2014-05-08 13:51 ` Christoph Lameter
2014-05-08 19:24 ` George Spelvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-07 6:06 [PATCH v2 00/10] clean-up and remove lockdep annotation in SLAB Joonsoo Kim
2014-05-07 6:06 ` [PATCH v2 03/10] slab: move up code to get kmem_cache_node in free_block() Joonsoo Kim
2014-05-08 0:52 ` David Rientjes
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=20140508192405.30677.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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).