[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200220195535.7xblt45akld6eftj@ca-dmjordan1.us.oracle.com>
Date: Thu, 20 Feb 2020 14:55:35 -0500
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Tejun Heo <tj@...nel.org>
Cc: Daniel Jordan <daniel.m.jordan@...cle.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <guro@...com>, linux-mm@...ck.org,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] mm: memcontrol: asynchronous reclaim for memory.high
On Thu, Feb 20, 2020 at 01:45:45PM -0500, Tejun Heo wrote:
> The setup cost can be lazy optimized but it'd still have to bounce the
> tiny pieces of work to different threads instead of processing them in
> one fell swoop from the same context, which most likely is gonna be
> untenably expensive.
I see, your last mail is clearer now. If it's easy to do, a pointer to where
this happens would help so we're on the same page.
thanks,
Daniel
Powered by blists - more mailing lists