lkml.org 
[lkml]   [2022]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: memcg reclaim demotion wrt. isolation
On Wed 14-12-22 10:57:52, Huang, Ying wrote:
> Michal Hocko <mhocko@suse.com> writes:
[...]
> > This makes sense but I suspect that this wasn't intended also for
> > memcg triggered reclaim. This would mean that a memory pressure in one
> > hierarchy could trigger paging out pages of a different hierarchy if the
> > demotion target is close to full.
>
> It seems that it's unnecessary to wake up kswapd of demotion target node
> in most cases. Because we will try to reclaim on the demotion target
> nodes in the loop of do_try_to_free_pages(). It may be better to loop
> the zonelist in the reverse order. Because the demotion targets are
> usually located at the latter of the zonelist.

Reclaiming from demotion targets first would deal with that as well.
Thanks! Let's establish whether this is something we really need/want
fix first.
--
Michal Hocko
SUSE Labs

\
 
 \ /
  Last update: 2022-12-14 10:50    [W:0.113 / U:0.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site