From: John Hubbard <jhubbard@nvidia.com>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: RFA (Request for Advice): block/bio: get_user_pages() --> pin_user_pages()
Date: Mon, 24 Jan 2022 13:06:03 -0800 [thread overview]
Message-ID: <923c30a5-747e-148b-43c9-32dfacda0d0a@nvidia.com> (raw)
In-Reply-To: <20220124100501.gwkaoohkm2b6h7xl@quack3.lan>
On 1/24/22 02:05, Jan Kara wrote:
...
>> do_direct_IO()
>> dio_zero_block()
>> page = ZERO_PAGE(0); <-- This is a problem
>>
>> I'm not sure what to use, instead of that zero page! The zero page
>> doesn't need to be allocated nor tracked, and so any replacement
>> approaches would need either other storage, or some horrid scheme that I
>> won't go so far as to write on the screen. :)
>
> Well, I'm not sure if you consider this ugly but currently we use
> get_page() in that path exactly so that bio_release_pages() does not have
> to care about zero page. So now we could grab pin on the zero page instead
> through try_grab_page() or something like that...
>
> Honza
So it sounds like you prefer this over checking for the zero page in
bio_release_pages(). I'll take a look at both ideas, then, and see what
it looks like.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2022-01-25 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 7:52 RFA (Request for Advice): block/bio: get_user_pages() --> pin_user_pages() John Hubbard
2022-01-24 10:05 ` Jan Kara
2022-01-24 10:38 ` Chaitanya Kulkarni
2022-01-24 12:19 ` Jan Kara
2022-01-24 19:34 ` John Hubbard
2022-01-24 21:06 ` Jan Kara
2022-01-24 21:06 ` John Hubbard [this message]
2022-01-24 22:17 ` Jan Kara
2022-01-24 13:18 ` Matthew Wilcox
2022-01-24 19:48 ` John Hubbard
2022-01-26 5:42 ` Chaitanya Kulkarni
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=923c30a5-747e-148b-43c9-32dfacda0d0a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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