From: Michal Hocko <mhocko@kernel.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 0/3] memdelay: memory health metric for systems and workloads
Date: Wed, 2 Aug 2017 10:11:36 +0200 [thread overview]
Message-ID: <20170802081136.GE2524@dhcp22.suse.cz> (raw)
In-Reply-To: <20170728194337.GA18981@cmpxchg.org>
On Fri 28-07-17 15:43:37, Johannes Weiner wrote:
> Hi Andrew,
>
> On Thu, Jul 27, 2017 at 01:43:25PM -0700, Andrew Morton wrote:
> > On Thu, 27 Jul 2017 11:30:07 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
> >
> > > This patch series implements a fine-grained metric for memory
> > > health.
> >
> > I assume some Documentation/ is forthcoming.
>
> Yep, I'll describe the interface and how to use this more extensively.
>
> > Consuming another page flag hurts. What's our current status there?
>
> I would say we can make it 64-bit only, but I also need this refault
> distinction flag in the LRU balancing patches [1] to apply pressure on
> anon pages only when the page cache is actually thrashing, not when
> it's just transitioning to another workingset. So let's see...
I didn't get to look at the patchset yet but just for this part. I guess
you can go without a new page flag. PG_slab could be reused with some
care AFAICS. Slab allocators do not seem to use other page flags so we
could make
bool PageSlab()
{
unsigned long flags = page->flags & ((1UL << NR_PAGEFLAGS) - 1);
return (flags & (1UL << PG_slab)) == (1UL << PG_slab);
}
and then reuse the same bit for working set pages. Page cache will
almost always have LRU bit set and workingset_eviction assumes PG_locked
so we will have another bit set when needed. I know this is fuggly and
subtle but basically everything about struct page is inevitably like
that...
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-08-02 8:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 15:30 Johannes Weiner
2017-07-27 15:30 ` [PATCH 1/3] sched/loadavg: consolidate LOAD_INT, LOAD_FRAC macros Johannes Weiner
2017-07-27 15:30 ` [PATCH 2/3] mm: workingset: tell cache transitions from workingset thrashing Johannes Weiner
2017-07-27 15:30 ` [PATCH 3/3] mm/sched: memdelay: memory health interface for systems and workloads Johannes Weiner
2017-07-27 15:56 ` Johannes Weiner
2017-07-29 9:10 ` Peter Zijlstra
2017-07-30 15:28 ` Johannes Weiner
2017-07-31 8:31 ` Peter Zijlstra
2017-07-31 18:41 ` Johannes Weiner
2017-07-31 19:49 ` Mike Galbraith
2017-07-31 20:38 ` Johannes Weiner
2017-08-01 2:23 ` Mike Galbraith
2017-08-01 7:57 ` Peter Zijlstra
2017-08-01 12:26 ` Johannes Weiner
2017-08-13 14:52 ` Peter Zijlstra
2017-07-29 13:31 ` kbuild test robot
2017-07-27 20:43 ` [PATCH 0/3] memdelay: memory health metric " Andrew Morton
2017-07-28 19:43 ` Johannes Weiner
2017-08-02 8:11 ` Michal Hocko [this message]
2017-07-29 2:48 ` Mike Galbraith
2017-07-29 3:21 ` Mike Galbraith
2017-07-29 6:38 ` Mike Galbraith
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=20170802081136.GE2524@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.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