linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Alexander Graf <graf@amazon.com>
Cc: Hillf Danton <hdanton@sina.com>,
	Alexander Duyck <alexander.duyck@gmail.com>,
	kvm@vger.kernel.org, mst@redhat.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, mgorman@techsingularity.net,
	Minchan Kim <minchan@kernel.org>,
	vbabka@suse.cz
Subject: Re: [PATCH v16.1 0/9] mm / virtio: Provide support for free page reporting
Date: Sat, 25 Jan 2020 10:01:26 +0800	[thread overview]
Message-ID: <20200125020126.3348-1-hdanton@sina.com> (raw)
In-Reply-To: <20200124132352.12824-1-hdanton@sina.com>


On Fri, 24 Jan 2020 17:40:51 +0100 Alexander Graf wrote:
> 
> On 24.01.20 14:23, Hillf Danton wrote:
> > 
> > On Thu, 23 Jan 2020 11:20:07 +0100 Alexander Graf wrote:
> >>
> >> The big problem I see is that what I really want from a user's point of
> >> view is a tuneable that says "Automatically free clean page cache pages
> >> that were not accessed in the last X minutes".
> > 
> > A diff is made on top of 1a4e58cce84e ("mm: introduce MADV_PAGEOUT") without
> > test in any form, assuming it goes in line with the tunable above but without
> > "X minutes" taken into account.
> > 
<snip>
> > 
> > --- a/include/uapi/asm-generic/mman-common.h
> > +++ b/include/uapi/asm-generic/mman-common.h
> > @@ -69,6 +69,7 @@
> >   
> >   #define MADV_COLD	20		/* deactivate these pages */
> >   #define MADV_PAGEOUT	21		/* reclaim these pages */
> > +#define MADV_CCPC	22		/* reclaim cold & clean page cache pages */
> 
> This patch adds a new madvise flag. I have a hard time seeing how that 
> would help with the "full system expiry" of pages?
> 
It works on the basis of individual process now. Shrinking all ccpc
pages in the system without memory pressure...they will be reclaimed
once memory becomes tight.

> The basic point that I tried to make above was that I would ideally like 
> to have a coldness cutoff date at which you can be pretty confident that 
> page cache data is no longer needed.
> 
The X minutes need another define like

	#define MADV_DCPC  23   /* deactivate clean page cache pages */

> To work properly, this needs to be transparent to any normal process on 
> the system :).

then task-A on the system can hint kernel like

	madvise(MADV_DCPC);	/* make clean pc pages cold */
	X minutes go by;	/* sieve out hot pages */
	madvise(MADV_CCPC);	/* shrink ccpc */



  parent reply	other threads:[~2020-01-25  2:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 17:43 Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 1/9] mm: Adjust shuffle code to allow for future coalescing Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 2/9] mm: Use zone and order instead of free area in free_list manipulators Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 3/9] mm: Add function __putback_isolated_page Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 4/9] mm: Introduce Reported pages Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 5/9] virtio-balloon: Pull page poisoning config out of free page hinting Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 6/9] virtio-balloon: Add support for providing free page reports to host Alexander Duyck
2020-02-11 11:03   ` David Hildenbrand
2020-02-11 11:47     ` Michael S. Tsirkin
2020-02-11 12:19       ` David Hildenbrand
2020-02-11 14:07         ` Michael S. Tsirkin
2020-02-11 14:31           ` David Hildenbrand
2020-02-11 14:48             ` Michael S. Tsirkin
2020-02-11 15:13               ` David Hildenbrand
2020-02-11 16:33                 ` Alexander Duyck
2020-02-11 17:04                   ` David Hildenbrand
2020-01-22 17:43 ` [PATCH v16.1 7/9] mm/page_reporting: Rotate reported pages to the tail of the list Alexander Duyck
2020-01-22 17:43 ` [PATCH v16.1 8/9] mm/page_reporting: Add budget limit on how many pages can be reported per pass Alexander Duyck
2020-01-22 17:44 ` [PATCH v16.1 9/9] mm/page_reporting: Add free page reporting documentation Alexander Duyck
2020-01-23 10:20 ` [PATCH v16.1 0/9] mm / virtio: Provide support for free page reporting Alexander Graf
2020-01-23 14:05   ` David Hildenbrand
2020-01-23 14:52     ` Alexander Graf
2020-01-24 13:25       ` David Hildenbrand
2020-01-24 16:20         ` David Hildenbrand
2020-01-23 16:26   ` Alexander Duyck
2020-01-23 16:54     ` Alexander Graf
2020-01-23 18:33       ` Alexander Duyck
2020-01-23 18:47         ` Graf (AWS), Alexander
2020-01-23 22:05           ` Alexander Duyck
2020-01-23 17:20     ` Dave Hansen
2020-01-23 19:23       ` Konrad Rzeszutek Wilk
2020-01-23 19:17     ` Johannes Weiner
2020-01-23 22:29       ` Alexander Duyck
2020-01-23 23:24         ` Dave Hansen
2020-01-24 13:23 ` Hillf Danton
2020-01-24 16:40   ` Alexander Graf
2020-01-25  2:01   ` Hillf Danton [this message]
2020-02-03 22:05 ` Alexander Duyck
2020-02-10 19:18   ` Should I repost? (was: Re: [PATCH v16.1 0/9] mm / virtio: Provide support for free page reporting) Alexander Duyck
2020-02-11 10:40     ` Mel Gorman
2020-02-11 22:57       ` Alexander Duyck

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=20200125020126.3348-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.duyck@gmail.com \
    --cc=graf@amazon.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@kernel.org \
    --cc=mst@redhat.com \
    --cc=vbabka@suse.cz \
    /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