[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b5b35fa-3c70-adc8-ca3a-4829388c4d12@kernel.dk>
Date: Sun, 27 Feb 2022 14:59:35 -0700
From: Jens Axboe <axboe@...nel.dk>
To: jhubbard.send.patches@...il.com, Jan Kara <jack@...e.cz>,
Christoph Hellwig <hch@...radead.org>,
Dave Chinner <dchinner@...hat.com>,
"Darrick J . Wong" <djwong@...nel.org>,
Theodore Ts'o <tytso@....edu>,
Alexander Viro <viro@...iv.linux.org.uk>,
Miklos Szeredi <miklos@...redi.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Chaitanya Kulkarni <kch@...dia.com>
Cc: linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
John Hubbard <jhubbard@...dia.com>
Subject: Re: [PATCH 4/6] block, bio, fs: convert most filesystems to
pin_user_pages_fast()
On 2/27/22 2:34 AM, jhubbard.send.patches@...il.com wrote:
> From: John Hubbard <jhubbard@...dia.com>
>
> Use pin_user_pages_fast(), pin_user_page(), and unpin_user_page() calls,
> in place of get_user_pages_fast(), get_page() and put_page().
>
> This converts the Direct IO parts of most filesystems over to using
> FOLL_PIN (pin_user_page*()) page pinning.
The commit message needs to explain why a change is being made, not what
is being done. The latter I can just look at the code for.
Didn't even find it in in your cover letter, had to go to the original
posting for that.
--
Jens Axboe
Powered by blists - more mailing lists