From: Ralph Campbell <rcampbell@nvidia.com>
To: Jan Kara <jack@suse.cz>
Cc: <linux-mm@kvack.org>, <linux-xfs@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-nvdimm@lists.01.org>,
<linux-kernel@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Matthew Wilcox <willy@infradead.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
Theodore Ts'o <tytso@mit.edu>, "Christoph Hellwig" <hch@lst.de>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ext4/xfs: add page refcount helper
Date: Wed, 7 Oct 2020 11:12:40 -0700 [thread overview]
Message-ID: <f8aff11f-3913-a0ac-b8cd-5380738a8e3c@nvidia.com> (raw)
In-Reply-To: <20201007082517.GC6984@quack2.suse.cz>
On 10/7/20 1:25 AM, Jan Kara wrote:
> On Tue 06-10-20 16:09:30, Ralph Campbell wrote:
>> There are several places where ZONE_DEVICE struct pages assume a reference
>> count == 1 means the page is idle and free. Instead of open coding this,
>> add a helper function to hide this detail.
>>
>> Signed-off-by: Ralph Campbell <rcampbell@nvidia.com>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Looks as sane direction but if we are going to abstract checks when
> ZONE_DEVICE page is idle, we should also update e.g.
> mm/swap.c:put_devmap_managed_page() or
> mm/gup.c:__unpin_devmap_managed_user_page() (there may be more places like
> this but I found at least these two...). Maybe Dan has more thoughts about
> this.
>
> Honza
I think this is a good point but I would like to make that a follow on
patch rather than add to this one.
next prev parent reply other threads:[~2020-10-07 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 23:09 [PATCH] ext4/xfs: add page refcount helper Ralph Campbell
2020-10-07 2:40 ` Dan Williams
2020-10-07 14:41 ` Theodore Y. Ts'o
2020-10-07 8:25 ` Jan Kara
2020-10-07 18:12 ` Ralph Campbell [this message]
2020-10-07 21:59 ` Dan Williams
2020-10-07 15:36 ` Darrick J. Wong
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=f8aff11f-3913-a0ac-b8cd-5380738a8e3c@nvidia.com \
--to=rcampbell@nvidia.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).