[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170813145227.eblt2ihn6wlqmcyn@hirez.programming.kicks-ass.net>
Date: Sun, 13 Aug 2017 16:52:27 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Johannes Weiner <hannes@...xchg.org>
Cc: Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
kernel-team@...com
Subject: Re: [PATCH 3/3] mm/sched: memdelay: memory health interface for
systems and workloads
On Tue, Aug 01, 2017 at 08:26:34AM -0400, Johannes Weiner wrote:
> On Tue, Aug 01, 2017 at 09:57:28AM +0200, Peter Zijlstra wrote:
> > And you haven't even defined wth a memdelay section is yet..
>
> It's what a task is in after it calls memdelay_enter() and before it
> calls memdelay_leave().
Urgh, yes that makes it harder to reusing existing bits.. although
delayacct seems to do something vaguely similar. I've never really
looked at that, but if you can reuse/merge that would of course be good.
Powered by blists - more mailing lists