Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-04 Thread Johannes Weiner
On Tue, Jun 04, 2019 at 08:02:05AM +0900, Minchan Kim wrote: > Hi Johannes, > > On Mon, Jun 03, 2019 at 05:50:59PM -0400, Johannes Weiner wrote: > > On Mon, Jun 03, 2019 at 10:32:30PM +0200, Michal Hocko wrote: > > > On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > > > > On Mon, Jun 03, 2019 at

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-04 Thread Michal Hocko
On Tue 04-06-19 13:26:51, Minchan Kim wrote: > On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: [...] > > Right. But there is still the page cache reclaim. Is it expected that > > an explicitly cold memory doesn't get reclaimed because we have a > > sufficient amount of page cache (a

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-04 Thread Michal Hocko
On Tue 04-06-19 08:02:05, Minchan Kim wrote: > Hi Johannes, > > On Mon, Jun 03, 2019 at 05:50:59PM -0400, Johannes Weiner wrote: > > On Mon, Jun 03, 2019 at 10:32:30PM +0200, Michal Hocko wrote: > > > On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > > > > On Mon, Jun 03, 2019 at 09:16:07AM

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-04 Thread Michal Hocko
On Mon 03-06-19 17:50:59, Johannes Weiner wrote: > On Mon, Jun 03, 2019 at 10:32:30PM +0200, Michal Hocko wrote: > > On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > > > On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > > > > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > > > >

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Minchan Kim
On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > > > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: >

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Minchan Kim
Hi Johannes, On Mon, Jun 03, 2019 at 05:50:59PM -0400, Johannes Weiner wrote: > On Mon, Jun 03, 2019 at 10:32:30PM +0200, Michal Hocko wrote: > > On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > > > On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > > > > On Fri 31-05-19 23:34:07,

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Johannes Weiner
On Mon, Jun 03, 2019 at 10:32:30PM +0200, Michal Hocko wrote: > On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > > On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > > > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > > > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Michal Hocko
On Mon 03-06-19 13:27:17, Johannes Weiner wrote: > On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > > > > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > > > > On

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Johannes Weiner
On Mon, Jun 03, 2019 at 09:16:07AM +0200, Michal Hocko wrote: > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > > > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: >

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Daniel Colascione
On Mon, Jun 3, 2019 at 12:16 AM Michal Hocko wrote: > On Fri 31-05-19 23:34:07, Minchan Kim wrote: > > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > > > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: > > > > >

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-06-03 Thread Michal Hocko
On Fri 31-05-19 23:34:07, Minchan Kim wrote: > On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: > > > > On Fri 31-05-19 15:43:08, Minchan Kim wrote: > > > > > When a

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-05-31 Thread Minchan Kim
On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote: > On Fri 31-05-19 22:39:04, Minchan Kim wrote: > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: > > > On Fri 31-05-19 15:43:08, Minchan Kim wrote: > > > > When a process expects no accesses to a certain memory range, it

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-05-31 Thread Michal Hocko
On Fri 31-05-19 22:39:04, Minchan Kim wrote: > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: > > On Fri 31-05-19 15:43:08, Minchan Kim wrote: > > > When a process expects no accesses to a certain memory range, it could > > > give a hint to kernel that the pages can be reclaimed

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-05-31 Thread Minchan Kim
On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote: > On Fri 31-05-19 15:43:08, Minchan Kim wrote: > > When a process expects no accesses to a certain memory range, it could > > give a hint to kernel that the pages can be reclaimed when memory pressure > > happens but data should be

Re: [RFCv2 1/6] mm: introduce MADV_COLD

2019-05-31 Thread Michal Hocko
On Fri 31-05-19 15:43:08, Minchan Kim wrote: > When a process expects no accesses to a certain memory range, it could > give a hint to kernel that the pages can be reclaimed when memory pressure > happens but data should be preserved for future use. This could reduce > workingset eviction so it

[RFCv2 1/6] mm: introduce MADV_COLD

2019-05-31 Thread Minchan Kim
When a process expects no accesses to a certain memory range, it could give a hint to kernel that the pages can be reclaimed when memory pressure happens but data should be preserved for future use. This could reduce workingset eviction so it ends up increasing performance. This patch introduces