From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>,
YASUAKI ISHIMATSU <yasu.isimatu@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, koki.sanagi@us.fujitsu.com,
Steve Sistare <steven.sistare@oracle.com>
Subject: Re: [PATCH] mm, meminit: Serially initialise deferred memory if trace_buf_size is specified
Date: Wed, 29 Nov 2017 22:49:45 -0500 [thread overview]
Message-ID: <CAOAebxsg=fM1B0sxKFenwShWTK1D2Xkcaw3qGD9dy6Lzw_iMLA@mail.gmail.com> (raw)
In-Reply-To: <20171120170429.315726fb004905314ced614e@linux-foundation.org>
>> Hi Mel,
>>
>> The forth approach is the best as it is seamless for admins and
>> engineers, it will also work on any system configuration with any
>> parameters without any special involvement.
>
> Apart from what-mel-said, I'd be concerned that this failsafe would
> almost never get tested. We should find some way to ensure that this
> code gets exercised in some people's kernels on a permanent basis and
> I'm not sure how to do that.
>
> One option might be to ask Fengguang to add the occasional
> test_pavels_stuff=1 to the kernel boot commandline. That's better
> than nothing but 0-day only runs on a small number of machine types.
>
Hi Andrew,
Excellent point about testing. I think, that if I implement it the way
I proposed in the previous e-mail:
1. initialize very few struct pages initially
2. initialize more as kernel needs them in every node
3. finally initialize all the rest when other cpus are started
We will have coverage for my code every time machine boots (and
deferred page init feature configured), as the the initial very few
struct pages is not going to be enough on any machine. Potentially, we
will also see some small boot time improvement because we will
initialize serially only as many pages as needed, and not do upper
bound guessing about how many pages is needed beforehand.
Thank you,
Pavel
--
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:[~2017-11-30 3:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 8:55 Mel Gorman
2017-11-15 11:55 ` Michal Hocko
2017-11-15 14:13 ` Mel Gorman
2017-11-15 14:28 ` Michal Hocko
2017-11-15 14:43 ` Mel Gorman
2017-11-15 14:57 ` Michal Hocko
2017-11-15 19:17 ` YASUAKI ISHIMATSU
2017-11-16 8:54 ` Michal Hocko
2017-11-16 10:06 ` Mel Gorman
2017-11-17 18:19 ` Pavel Tatashin
2017-11-17 21:32 ` Mel Gorman
2017-11-30 3:41 ` Pavel Tatashin
2017-12-06 10:50 ` Mel Gorman
2018-01-31 17:28 ` Koki.Sanagi
2018-01-31 18:24 ` Pavel Tatashin
2018-02-05 14:14 ` Masayoshi Mizuma
2018-02-05 15:26 ` Pavel Tatashin
2017-11-21 1:04 ` Andrew Morton
2017-11-30 3:49 ` Pavel Tatashin [this message]
2017-11-15 19:49 ` Andrew Morton
2017-11-16 8:39 ` Mel Gorman
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='CAOAebxsg=fM1B0sxKFenwShWTK1D2Xkcaw3qGD9dy6Lzw_iMLA@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=koki.sanagi@us.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=steven.sistare@oracle.com \
--cc=yasu.isimatu@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