Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma

2018-11-23 Thread Vlastimil Babka
On 11/23/18 4:21 PM, Michal Hocko wrote: > On Fri 23-11-18 16:07:06, Vlastimil Babka wrote: >> On 11/20/18 11:35 AM, Michal Hocko wrote: >>> From: Michal Hocko >>> >>> Userspace falls short when trying to find out whether a specific memory >>> range is eligible for THP. There are usecases that

Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma

2018-11-23 Thread Michal Hocko
On Fri 23-11-18 16:07:06, Vlastimil Babka wrote: > On 11/20/18 11:35 AM, Michal Hocko wrote: > > From: Michal Hocko > > > > Userspace falls short when trying to find out whether a specific memory > > range is eligible for THP. There are usecases that would like to know > > that > >

Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma

2018-11-23 Thread Vlastimil Babka
On 11/20/18 11:35 AM, Michal Hocko wrote: > From: Michal Hocko > > Userspace falls short when trying to find out whether a specific memory > range is eligible for THP. There are usecases that would like to know > that >

Re: [RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma

2018-11-20 Thread Michal Hocko
Damn, David somehow didn't make it to the CC list. Sorry about that. On Tue 20-11-18 11:35:14, Michal Hocko wrote: > From: Michal Hocko > > Userspace falls short when trying to find out whether a specific memory > range is eligible for THP. There are usecases that would like to know > that >

[RFC PATCH 2/3] mm, thp, proc: report THP eligibility for each vma

2018-11-20 Thread Michal Hocko
From: Michal Hocko Userspace falls short when trying to find out whether a specific memory range is eligible for THP. There are usecases that would like to know that http://lkml.kernel.org/r/alpine.deb.2.21.1809251248450.50...@chino.kir.corp.google.com : This is used to identify heap mappings