From: Andrew Morton <akpm@linux-foundation.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>, Jan Kara <jack@suse.cz>,
Logan Gunthorpe <logang@deltatee.com>,
<linux-block@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-xfs@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
<linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] block: add dio_w_*() wrappers for pin, unpin user pages
Date: Sat, 27 Aug 2022 15:27:45 -0700 [thread overview]
Message-ID: <20220827152745.3dcd05e98b3a4383af650a72@linux-foundation.org> (raw)
In-Reply-To: <20220827083607.2345453-3-jhubbard@nvidia.com>
On Sat, 27 Aug 2022 01:36:03 -0700 John Hubbard <jhubbard@nvidia.com> wrote:
> Background: The Direct IO part of the block infrastructure is being
> changed to use pin_user_page*() and unpin_user_page*() calls, in place
> of a mix of get_user_pages_fast(), get_page(), and put_page(). These
> have to be changed over all at the same time, for block, bio, and all
> filesystems. However, most filesystems can be changed via iomap and core
> filesystem routines, so let's get that in place, and then continue on
> with converting the remaining filesystems (9P, CIFS) and anything else
> that feeds pages into bio that ultimately get released via
> bio_release_pages().
>
> Add a new config parameter, CONFIG_BLK_USE_PIN_USER_PAGES_FOR_DIO, and
> dio_w_*() wrapper functions. The dio_w_ prefix was chosen for
> uniqueness, so as to ease a subsequent kernel-wide rename via
> search-and-replace. Together, these allow the developer to choose
> between these sets of routines, for Direct IO code paths:
>
> a) pin_user_pages_fast()
> pin_user_page()
> unpin_user_page()
>
> b) get_user_pages_fast()
> get_page()
> put_page()
>
> CONFIG_BLK_USE_PIN_USER_PAGES_FOR_DIO is a temporary setting, and may
> be deleted once the conversion is complete. In the meantime, developers
> can enable this in order to try out each filesystem.
>
> Please remember that these /proc/vmstat items (below) should normally
> contain the same values as each other, except during the middle of
> pin/unpin operations. As such, they can be helpful when monitoring test
> runs:
>
> nr_foll_pin_acquired
> nr_foll_pin_released
>
> ...
>
> +static inline void dio_w_unpin_user_pages(struct page **pages,
> + unsigned long npages)
> +{
> + unsigned long i;
> +
> + for (i = 0; i < npages; i++)
> + put_page(pages[i]);
> +}
release_pages()? Might be faster if many of the pages are page_count()==1.
(release_pages() was almost as simple as the above when I added it a
million years ago. But then progress happened).
next prev parent reply other threads:[~2022-08-27 22:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 8:36 [PATCH 0/6] convert most filesystems to pin_user_pages_fast() John Hubbard
2022-08-27 8:36 ` [PATCH 1/6] mm/gup: introduce pin_user_page() John Hubbard
2022-08-29 12:07 ` David Hildenbrand
2022-08-29 19:33 ` John Hubbard
2022-08-30 12:17 ` David Hildenbrand
2022-08-30 21:42 ` John Hubbard
2022-08-31 0:06 ` John Hubbard
2022-08-27 8:36 ` [PATCH 2/6] block: add dio_w_*() wrappers for pin, unpin user pages John Hubbard
2022-08-27 22:27 ` Andrew Morton [this message]
2022-08-27 23:59 ` John Hubbard
2022-08-28 0:12 ` Andrew Morton
2022-08-28 0:31 ` John Hubbard
2022-08-28 1:07 ` John Hubbard
2022-08-27 8:36 ` [PATCH 3/6] iov_iter: new iov_iter_pin_pages*() routines John Hubbard
2022-08-27 22:46 ` Al Viro
2022-08-27 22:48 ` John Hubbard
2022-08-27 8:36 ` [PATCH 4/6] block, bio, fs: convert most filesystems to pin_user_pages_fast() John Hubbard
2022-08-27 8:36 ` [PATCH 5/6] NFS: direct-io: convert to FOLL_PIN pages John Hubbard
2022-08-27 22:48 ` Al Viro
2022-08-27 23:55 ` John Hubbard
2022-08-28 0:38 ` Al Viro
2022-08-28 0:39 ` Al Viro
2022-08-28 0:46 ` John Hubbard
2022-08-29 4:59 ` John Hubbard
2022-08-29 16:08 ` Jan Kara
2022-08-29 19:59 ` John Hubbard
2022-08-31 9:43 ` Jan Kara
2022-08-31 18:02 ` John Hubbard
2022-09-01 0:38 ` Al Viro
2022-09-01 9:06 ` Jan Kara
2022-08-27 8:36 ` [PATCH 6/6] fuse: convert direct IO paths to use FOLL_PIN John Hubbard
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=20220827152745.3dcd05e98b3a4383af650a72@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=axboe@kernel.dk \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/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