lkml.org 
[lkml]   [2017]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH 2/2] Add /proc/PID/{smaps, numa_maps} support for DAX
On Thu, Oct 26, 2017 at 9:00 PM, Du, Fan <fan.du@intel.com> wrote:
>
>
>>-----Original Message-----
>>From: linux-kernel-owner@vger.kernel.org
>>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dave Hansen
>>Sent: Thursday, October 26, 2017 10:51 PM
>>To: Michal Hocko <mhocko@kernel.org>
>>Cc: Du, Fan <fan.du@intel.com>; akpm@linux-foundation.org; hch@lst.de;
>>Williams, Dan J <dan.j.williams@intel.com>; linux-kernel@vger.kernel.org;
>>linux-api@vger.kernel.org
>>Subject: Re: [PATCH 2/2] Add /proc/PID/{smaps, numa_maps} support for DAX
>>
>>On 10/26/2017 07:31 AM, Michal Hocko wrote:
>>> On Thu 26-10-17 07:24:14, Dave Hansen wrote:
>>>> Actually, I don't remember whether it was tooling or just confused
>>>> humans. I *think* Dan was trying to write test cases for huge page DAX
>>>> support and couldn't figure out whether or not it was using large pages.
>>>
>>> That sounds like a very weak justification to adding new stuff to smaps
>>> to be honest.
>>
>>Yep, agreed. It can't go in _just_ for DAX, and Fan and the other DAX
>>folks need to elaborate on their needs here.
>
> If user creates device DAX /dev/dax with some capacity like 512G, mmap it and
> Use it will, or touched 128G. To my best knowledge at this part, there is no
> statistics reported how much memory behind DAX actually used.
>
> This is the problem our customer is facing right now.

I'm not sure I understand, DAX is statically allocated. There's no
private memory taken from the page allocator to back device-dax
mappings. Unless you are trying to determine memory usage of page
tables?

\
 
 \ /
  Last update: 2017-10-28 20:17    [W:0.052 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site