linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Pavel Tatashin <pasha.tatashin@oracle.com>,
	linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [v1 0/5] parallelized "struct page" zeroing
Date: Fri, 24 Mar 2017 10:35:55 +0100	[thread overview]
Message-ID: <20170324093555.GB5891@osiris> (raw)
In-Reply-To: <341568c3-0473-860f-aa20-63723aa40b87@de.ibm.com>

On Fri, Mar 24, 2017 at 09:51:09AM +0100, Christian Borntraeger wrote:
> On 03/24/2017 12:01 AM, Pavel Tatashin wrote:
> > When deferred struct page initialization feature is enabled, we get a
> > performance gain of initializing vmemmap in parallel after other CPUs are
> > started. However, we still zero the memory for vmemmap using one boot CPU.
> > This patch-set fixes the memset-zeroing limitation by deferring it as well.
> > 
> > Here is example performance gain on SPARC with 32T:
> > base
> > https://hastebin.com/ozanelatat.go
> > 
> > fix
> > https://hastebin.com/utonawukof.go
> > 
> > As you can see without the fix it takes: 97.89s to boot
> > With the fix it takes: 46.91 to boot.
> > 
> > On x86 time saving is going to be even greater (proportionally to memory size)
> > because there are twice as many "struct page"es for the same amount of memory,
> > as base pages are twice smaller.
> 
> Fixing the linux-s390 mailing list email.
> This might be useful for s390 as well.

Unfortunately only for the fake numa case, since as far as I understand it,
parallelization happens only on a node granularity. And since we are
usually only having one node...

But anyway, it won't hurt to set ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT on
s390 also. I'll do some testing and then we'll see.

Pavel, could you please change your patch 5 so it also converts the s390
call sites of vmemmap_alloc_block() so they use VMEMMAP_ZERO instead of
'true' as argument?

      reply	other threads:[~2017-03-24  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 23:01 [v1 0/5] parallelized "struct page" zeroing Pavel Tatashin
2017-03-23 23:01 ` [v1 1/5] sparc64: simplify vmemmap_populate Pavel Tatashin
2017-03-23 23:01 ` [v1 2/5] mm: defining memblock_virt_alloc_try_nid_raw Pavel Tatashin
2017-03-23 23:01 ` [v1 3/5] mm: add "zero" argument to vmemmap allocators Pavel Tatashin
2017-03-23 23:01 ` [v1 4/5] mm: zero struct pages during initialization Pavel Tatashin
2017-03-23 23:01 ` [v1 5/5] mm: teach platforms not to zero struct pages memory Pavel Tatashin
2017-03-23 23:26 ` [v1 0/5] parallelized "struct page" zeroing Matthew Wilcox
2017-03-23 23:35   ` David Miller
2017-03-23 23:47     ` Pasha Tatashin
2017-03-24  1:15       ` Pasha Tatashin
2017-03-23 23:36   ` Pasha Tatashin
2017-03-24  8:51 ` Christian Borntraeger
2017-03-24  9:35   ` Heiko Carstens [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=20170324093555.GB5891@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=pasha.tatashin@oracle.com \
    --cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).