From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH RESEND v4 1/3] mm/sparse: optimize sparse_index_alloc
Date: Tue, 24 Jul 2012 08:54:45 +0800 [thread overview]
Message-ID: <20120724005445.GA4393@shangw.(null)> (raw)
In-Reply-To: <juj1bs$qh3$1@dough.gmane.org>
On Mon, Jul 23, 2012 at 08:18:04AM +0000, Cong Wang wrote:
>On Mon, 23 Jul 2012 at 02:31 GMT, Gavin Shan <shangw@linux.vnet.ibm.com> wrote:
>> With CONFIG_SPARSEMEM_EXTREME, the two level of memory section
>> descriptors are allocated from slab or bootmem. When allocating
>> from slab, let slab/bootmem allocator to clear the memory chunk.
>> We needn't clear that explicitly.
>>
>> Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
>> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>> Acked-by: David Rientjes <rientjes@google.com>
>
>Reviewed-by: Cong Wang <xiyou.wangcong@gmail.com>
>
Thanks for your time, Cong :-)
Thanks,
Gavin
>
>--
>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>
>
--
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>
prev parent reply other threads:[~2012-07-24 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 2:31 [PATCH RESEND v4 1/3] mm/sparse: optimize sparse_index_alloc Gavin Shan
2012-07-23 2:31 ` [PATCH RESEND v4 2/3] mm/sparse: more check on mem_section number Gavin Shan
2012-07-23 8:21 ` Cong Wang
2012-07-23 2:31 ` [PATCH RESEND v2 3/3] mm/sparse: remove index_init_lock Gavin Shan
2012-07-23 8:20 ` Cong Wang
2012-07-23 8:18 ` [PATCH RESEND v4 1/3] mm/sparse: optimize sparse_index_alloc Cong Wang
2012-07-24 0:54 ` Gavin Shan
2012-07-24 0:54 ` Gavin Shan [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='20120724005445.GA4393@shangw.(null)' \
--to=shangw@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--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 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).