From: Michal Hocko <mhocko@suse.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux.com>,
Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: fix draining remote pageset
Date: Wed, 16 Aug 2023 08:49:12 +0200 [thread overview]
Message-ID: <ZNxxaFnM9W8+imHD@dhcp22.suse.cz> (raw)
In-Reply-To: <87r0o6bcyw.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Mon 14-08-23 09:59:51, Huang, Ying wrote:
> Hi, Michal,
>
> Michal Hocko <mhocko@suse.com> writes:
>
> > On Fri 11-08-23 17:08:19, Huang Ying wrote:
> >> If there is no memory allocation/freeing in the remote pageset after
> >> some time (3 seconds for now), the remote pageset will be drained to
> >> avoid memory wastage.
> >>
> >> But in the current implementation, vmstat updater worker may not be
> >> re-queued when we are waiting for the timeout (pcp->expire != 0) if
> >> there are no vmstat changes, for example, when CPU goes idle.
> >
> > Why is that a problem?
>
> The pages of the remote zone may be kept in the local per-CPU pageset
> for long time as long as there's no page allocation/freeing on the
> logical CPU. In addition to the logical CPU goes idle, this is also
> possible if the logical CPU is busy in the user space.
But why is this a problem? Is the scale of the problem sufficient to
trigger out of memory situations or be otherwise harmful?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-08-16 6:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 9:08 Huang Ying
2023-08-11 9:35 ` Michal Hocko
2023-08-14 1:59 ` Huang, Ying
2023-08-16 6:49 ` Michal Hocko [this message]
2023-08-16 7:08 ` Huang, Ying
2023-08-16 20:23 ` Lameter, Christopher
2023-08-21 7:55 ` Michal Hocko
2023-08-21 8:30 ` Huang, Ying
2023-08-21 9:27 ` Michal Hocko
2023-08-21 22:31 ` Huang, Ying
2023-08-22 8:09 ` Michal Hocko
2023-08-25 17:06 ` Lameter, Christopher
2023-08-29 6:08 ` Huang, Ying
2023-08-29 18:05 ` Lameter, Christopher
2023-09-05 16:52 ` Vlastimil Babka
2023-09-06 4:17 ` Huang, Ying
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=ZNxxaFnM9W8+imHD@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=vbabka@suse.cz \
--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
all inboxes | Powered by JetHome®