From: Andrea Arcangeli <aarcange@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: ethan zhao <ethan.kernel@gmail.com>,
linux-kernel@vger.kernel.org, Mel Gorman <mgorman@suse.de>
Subject: Re: Huge memory takes too long time to initialize on 4TB ?
Date: Thu, 24 May 2012 01:32:41 +0200 [thread overview]
Message-ID: <20120523233240.GD4071@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205222035591.28165@chino.kir.corp.google.com>
Hi,
On Tue, May 22, 2012 at 08:38:04PM -0700, David Rientjes wrote:
> On Wed, 23 May 2012, ethan zhao wrote:
>
> > Hi, aarcange
> >
> > When I boot kernel 2.6.39-100.6.1.el6uek.x86_64(actually 3.0.26)on
> > a 4TB memory machine, got following call trace,
> > That shows huge memory take too long time to initialize ? any help ?,
> > I compared the huge_memory.c code between 3.0.26 and the current
> > 3.2.x, no change.
> >
>
> This has nothing to do with mm/huge_memory.c, which is transparent
> hugepages code, it's the lengthy iteration done for a very large
> ZONE_NORMAL in setup_zone_migrate_reserve().
>
> This should be fixed by 938929f14cb5 ("mm: reduce the amount of work done
> when updating min_free_kbytes") and was merged in 3.3. Let us know if
> there's still a problem after upgrading to either that or 3.4
I thought that was only a performance optimization, so if the oops is
generated by a timeout it can fix it, so good idea to try it. But a
timeout watchdog triggering exactly in spin_unlock sounds a bit
unlikely occurence, so I assumed too long time here meant "wait forever
because it crashed".
next prev parent reply other threads:[~2012-05-23 23:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 2:43 Huge memory takes too long time to initialize on 4TB ? ethan zhao
2012-05-23 3:38 ` David Rientjes
2012-05-23 23:32 ` Andrea Arcangeli [this message]
2012-05-24 0:32 ` David Rientjes
2012-05-24 2:18 ` ethan zhao
2012-05-24 4:48 ` David Rientjes
2012-05-24 14:32 ` ethan zhao
2012-05-24 16:22 ` Andrea Arcangeli
2012-05-24 2:28 ` ethan zhao
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=20120523233240.GD4071@redhat.com \
--to=aarcange@redhat.com \
--cc=ethan.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--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