From: Michal Hocko <mhocko@suse.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Donet Tom <donettom@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Mel Gorman <mgorman@suse.de>,
Ben Widawsky <ben.widawsky@intel.com>,
Feng Tang <feng.tang@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Rik van Riel <riel@surriel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@infradead.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Dan Williams <dan.j.williams@intel.com>,
Hugh Dickins <hughd@google.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH 1/3] mm/mempolicy: Use the already fetched local variable
Date: Tue, 20 Feb 2024 10:03:48 +0100 [thread overview]
Message-ID: <ZdRq9EM1mDFXBiiO@tiehlicka> (raw)
In-Reply-To: <8734tnppls.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Tue 20-02-24 15:22:07, Huang, Ying wrote:
[...]
> This isn't an issue now, because mpol_misplaced() are always called with
> PTL held. And, we can still keep thiscpu local variable.
yes, this is the case but it would be better if we made that assumption
official by lockdep_assert_held
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-02-20 9:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 7:31 Donet Tom
2024-02-17 7:31 ` [PATCH 3/3] mm/numa_balancing:Allow migrate on protnone reference with MPOL_PREFERRED_MANY policy Donet Tom
2024-02-19 12:07 ` Michal Hocko
2024-02-19 13:44 ` Donet Tom
2024-02-20 6:36 ` Huang, Ying
2024-02-20 6:44 ` Aneesh Kumar K.V
2024-02-20 7:23 ` Huang, Ying
2024-02-20 7:46 ` Aneesh Kumar K.V
2024-02-20 8:01 ` Huang, Ying
2024-02-19 14:20 ` Michal Hocko
2024-02-19 15:07 ` Donet Tom
2024-02-19 19:12 ` Michal Hocko
2024-02-20 3:57 ` Aneesh Kumar K.V
2024-02-20 8:48 ` Michal Hocko
2024-02-26 13:09 ` Donet Tom
2024-02-20 7:18 ` Huang, Ying
2024-02-20 7:53 ` Aneesh Kumar K.V
2024-02-20 7:58 ` Huang, Ying
2024-03-03 6:16 ` Aneesh Kumar K.V
2024-03-04 1:59 ` Huang, Ying
2024-02-18 21:38 ` [PATCH 1/3] mm/mempolicy: Use the already fetched local variable Andrew Morton
2024-02-19 8:34 ` Donet Tom
2024-02-20 1:21 ` Andrew Morton
2024-02-20 4:10 ` Aneesh Kumar K.V
2024-02-20 6:25 ` Huang, Ying
2024-02-20 6:32 ` Aneesh Kumar K.V
2024-02-20 7:03 ` Aneesh Kumar K.V
2024-02-20 7:22 ` Huang, Ying
2024-02-20 9:03 ` Michal Hocko [this message]
2024-03-03 6:17 ` Aneesh Kumar K.V
2024-03-04 1:49 ` Huang, Ying
[not found] ` <bf7e6779f842fb65cf7bb9b2c617feb2af271cb7.1708097962.git.donettom@linux.ibm.com>
2024-02-19 12:02 ` [PATCH 2/3] mm/mempolicy: Avoid the fallthrough with MPOLD_BIND in mpol_misplaced Michal Hocko
2024-02-19 15:18 ` Donet Tom
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=ZdRq9EM1mDFXBiiO@tiehlicka \
--to=mhocko@suse.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=donettom@linux.ibm.com \
--cc=feng.tang@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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