From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
mhocko@suse.com, jweiner@fb.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm, show_mem: drop pgdat_resize_lock in show_mem()
Date: Thu, 29 Nov 2018 01:52:05 +0000 [thread overview]
Message-ID: <20181129015205.rrwzakileopkrxaa@master> (raw)
In-Reply-To: <20181128140751.e79de952a3fdfdac3aab75e9@linux-foundation.org>
On Wed, Nov 28, 2018 at 02:07:51PM -0800, Andrew Morton wrote:
>On Thu, 29 Nov 2018 05:08:15 +0800 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> Function show_mem() is used to print system memory status when user
>> requires or fail to allocate memory. Generally, this is a best effort
>> information and not willing to affect core mm subsystem.
>>
>> The data protected by pgdat_resize_lock is mostly correct except there is:
>>
>> * page struct defer init
>> * memory hotplug
>
>What is the advantage in doing this? What problem does the taking of
>that lock cause?
Michal and I had a discussion in https://patchwork.kernel.org/patch/10689759/
The purpose of this is to see whehter it is nessary to make
pgdat_resize_lock IRQ context safe. After went through the code, most of
the users are not from IRQ context.
If my understanding is correct, Michal's suggestion is to drop the lock
here. (The second last reply from Michal.)
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2018-11-29 1:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:08 Wei Yang
2018-11-28 22:07 ` Andrew Morton
2018-11-29 1:52 ` Wei Yang [this message]
2018-11-29 8:17 ` Michal Hocko
2018-11-29 9:32 ` Wei Yang
2018-11-29 15:04 ` Wei Yang
2018-11-29 15:49 ` Michal Hocko
2018-11-29 16:05 ` Wei Yang
2018-11-29 16:18 ` Michal Hocko
2018-11-29 23:49 ` Wei Yang
2018-11-29 23:55 ` [PATCH v2] " Wei Yang
2018-11-30 8:17 ` Michal Hocko
2018-11-30 8:54 ` osalvador
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=20181129015205.rrwzakileopkrxaa@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jweiner@fb.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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