From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
Dave Hansen <dave.hansen@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps
Date: Tue, 15 Nov 2016 19:50:15 +0100 [thread overview]
Message-ID: <20161115185015.GA5854@lst.de> (raw)
In-Reply-To: <CAPcyv4hTchhsNXhKx6WpUWsvFyZjzJ4sx1emLCSU2iDKSMG1hA@mail.gmail.com>
Hi Dan,
On Mon, Nov 14, 2016 at 07:14:22PM -0800, Dan Williams wrote:
> Wanted to get your opinion on this given your earlier concerns about
> the VM_DAX flag.
>
> This instead lets an application know how much of a vma is backed by
> ZONE_DEVICE pages, but does not make any indications about the vma
> having DAX semantics or not. I.e. it is possible that 'device' and
> 'device_huge' are non-zero *and* vma_is_dax() is false. So, it is
> purely accounting the composition of the present pages in the vma.
>
> Another option is to have something like 'shared_thp' just to account
> for file backed huge pages that dax can map. However if ZONE_DEVICE
> is leaking into other use cases I think it makes sense to have it be a
> first class-citizen with respect to accounting alongside
> 'anonymous_thp'.
This counter sounds fine to me, it's a debug tool and not an obvious
abuse candidate like VM_DAX. But I'll defer to the VM folks for a real
review.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
Dave Hansen <dave.hansen@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps
Date: Tue, 15 Nov 2016 19:50:15 +0100 [thread overview]
Message-ID: <20161115185015.GA5854@lst.de> (raw)
In-Reply-To: <CAPcyv4hTchhsNXhKx6WpUWsvFyZjzJ4sx1emLCSU2iDKSMG1hA@mail.gmail.com>
Hi Dan,
On Mon, Nov 14, 2016 at 07:14:22PM -0800, Dan Williams wrote:
> Wanted to get your opinion on this given your earlier concerns about
> the VM_DAX flag.
>
> This instead lets an application know how much of a vma is backed by
> ZONE_DEVICE pages, but does not make any indications about the vma
> having DAX semantics or not. I.e. it is possible that 'device' and
> 'device_huge' are non-zero *and* vma_is_dax() is false. So, it is
> purely accounting the composition of the present pages in the vma.
>
> Another option is to have something like 'shared_thp' just to account
> for file backed huge pages that dax can map. However if ZONE_DEVICE
> is leaking into other use cases I think it makes sense to have it be a
> first class-citizen with respect to accounting alongside
> 'anonymous_thp'.
This counter sounds fine to me, it's a debug tool and not an obvious
abuse candidate like VM_DAX. But I'll defer to the VM folks for a real
review.
next prev parent reply other threads:[~2016-11-15 18:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 22:11 [PATCH] mm: add ZONE_DEVICE statistics to smaps Dan Williams
2016-11-10 22:11 ` Dan Williams
2016-11-10 22:11 ` Dan Williams
2016-11-11 4:12 ` Anshuman Khandual
2016-11-11 4:12 ` Anshuman Khandual
2016-11-11 4:12 ` Anshuman Khandual
2016-11-15 3:14 ` Dan Williams
2016-11-15 3:14 ` Dan Williams
2016-11-15 3:14 ` Dan Williams
2016-11-15 18:50 ` Christoph Hellwig [this message]
2016-11-15 18:50 ` Christoph Hellwig
[not found] ` <147881591739.39198.1358237993213024627.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-11-16 0:04 ` Andrew Morton
2016-11-16 0:04 ` Andrew Morton
2016-11-16 0:04 ` Andrew Morton
2016-11-16 0:15 ` Dave Hansen
2016-11-16 0:15 ` Dave Hansen
2016-11-16 0:15 ` Dave Hansen
2016-11-16 0:48 ` Dan Williams
2016-11-16 0:48 ` Dan Williams
2016-11-16 0:48 ` Dan Williams
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=20161115185015.GA5854@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.