From: Peter Zijlstra <peterz@infradead.org>
To: "zhangpeng (AS)" <zhangpeng362@huawei.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, Matthew Wilcox <willy@infradead.org>,
lstoakes@gmail.com, hughd@google.com, david@redhat.com,
fengwei.yin@intel.com, vbabka@suse.cz, mgorman@suse.de,
mingo@redhat.com, riel@redhat.com, ying.huang@intel.com,
hannes@cmpxchg.org, Nanyong Sun <sunnanyong@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [Question]: major faults are still triggered after mlockall when numa balancing
Date: Thu, 9 Nov 2023 15:11:41 +0100 [thread overview]
Message-ID: <20231109141141.GC8683@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <9e62fd9a-bee0-52bf-50a7-498fa17434ee@huawei.com>
On Thu, Nov 09, 2023 at 09:47:24PM +0800, zhangpeng (AS) wrote:
> Is there any way to avoid such a major fault?
man madvise
next prev parent reply other threads:[~2023-11-09 14:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:47 zhangpeng (AS)
2023-11-09 14:11 ` Peter Zijlstra [this message]
2023-11-09 14:29 ` Matthew Wilcox
2023-11-09 15:15 ` Yin, Fengwei
2023-11-09 17:27 ` Matthew Wilcox
2023-11-10 5:32 ` Huang, Ying
2023-11-10 9:04 ` Yin, Fengwei
2023-11-13 2:02 ` Huang, Ying
2023-11-14 11:23 ` Yin, Fengwei
2023-11-15 1:46 ` Huang, Ying
2023-11-10 9:39 ` zhangpeng (AS)
2023-11-09 22:54 ` Yang Shi
2023-11-10 1:57 ` Yin, Fengwei
2023-11-10 3:39 ` Kefeng Wang
2023-11-10 3:50 ` Yin, Fengwei
2023-11-10 4:00 ` Aneesh Kumar K V
2023-11-14 1:41 ` Yang Shi
2023-11-14 11:10 ` Yin, Fengwei
2023-11-09 23:21 ` Matthew Wilcox
2023-11-10 5:04 ` Aneesh Kumar K.V
2023-11-10 8:36 ` zhangpeng (AS)
2023-11-10 8:17 ` Aneesh Kumar K.V
2023-11-10 9:50 ` zhangpeng (AS)
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=20231109141141.GC8683@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=sunnanyong@huawei.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=zhangpeng362@huawei.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