From: Vlastimil Babka <vbabka@suse.cz>
To: Arun KS <arunks@codeaurora.org>,
akpm@linux-foundation.org, keescook@chromium.org,
khlebnikov@yandex-team.ru, minchan@kernel.org, mhocko@kernel.org,
osalvador@suse.de, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Cc: getarunks@gmail.com
Subject: Re: [PATCH v3 1/4] mm: reference totalram_pages and managed_pages once per function
Date: Thu, 8 Nov 2018 12:44:53 +0100 [thread overview]
Message-ID: <bceb1841-885f-a35a-b4a0-522f588af956@suse.cz> (raw)
In-Reply-To: <1541665398-29925-2-git-send-email-arunks@codeaurora.org>
On 11/8/18 9:23 AM, Arun KS wrote:
> This patch is in preparation to a later patch which converts totalram_pages
> and zone->managed_pages to atomic variables. Please note that re-reading
> the value might lead to a different value and as such it could lead to
> unexpected behavior. There are no known bugs as a result of the current code
> but it is better to prevent from them in principle.
..., which will happen after the atomic conversion in the next patch.
> Signed-off-by: Arun KS <arunks@codeaurora.org>
> Reviewed-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> Acked-by: Michal Hocko <mhocko@suse.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
next prev parent reply other threads:[~2018-11-08 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 8:23 [PATCH v3 0/4] mm: convert totalram_pages, totalhigh_pages and managed pages to atomic Arun KS
2018-11-08 8:23 ` [PATCH v3 1/4] mm: reference totalram_pages and managed_pages once per function Arun KS
2018-11-08 11:44 ` Vlastimil Babka [this message]
2018-11-09 11:33 ` kbuild test robot
2018-11-08 8:23 ` [PATCH v3 2/4] mm: convert zone->managed_pages to atomic variable Arun KS
2018-11-08 8:32 ` Michal Hocko
2018-11-08 8:23 ` [PATCH v3 3/4] mm: convert totalram_pages and totalhigh_pages variables to atomic Arun KS
2018-11-08 8:23 ` [PATCH v3 4/4] mm: Remove managed_page_count spinlock Arun KS
2018-11-08 8:34 ` Michal Hocko
2018-11-08 10:03 ` Arun KS
2018-11-08 10:14 ` Michal Hocko
2018-11-08 10:31 ` Arun KS
2018-11-09 15:42 ` Arun KS
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=bceb1841-885f-a35a-b4a0-522f588af956@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=getarunks@gmail.com \
--cc=keescook@chromium.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=osalvador@suse.de \
/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).