From: Jens Axboe <axboe@kernel.dk>
To: David Howells <dhowells@redhat.com>, Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
Logan Gunthorpe <logang@deltatee.com>,
Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 7/7] iov_iter, block: Make bio structs pin pages rather than ref'ing if appropriate
Date: Mon, 9 Jan 2023 14:57:36 -0700 [thread overview]
Message-ID: <d0bb04e7-7e58-d494-0e39-6e98f3368a7b@kernel.dk> (raw)
In-Reply-To: <2008444.1673300255@warthog.procyon.org.uk>
On 1/9/23 2:37?PM, David Howells wrote:
> Jan Kara <jack@suse.cz> wrote:
>
>> So currently we already have BIO_NO_PAGE_REF flag and what you do in this
>> patch partially duplicates that. So either I'd drop that flag or instead of
>> bi_cleanup_mode variable (which honestly looks a bit wasteful given how we
>> microoptimize struct bio) just add another BIO_ flag...
>
> I'm fine with translating the FOLL_* flags to the BIO_* flags. I could add a
> BIO_PAGE_PINNED and translate:
>
> FOLL_GET => 0
> FOLL_PIN => BIO_PAGE_PINNED
> 0 => BIO_NO_PAGE_REF
>
> It would seem that BIO_NO_PAGE_REF can't be set for BIO_PAGE_PINNED because
> BIO_NO_PAGE_REF governs whether bio_release_pages() calls
> __bio_release_pages() - which would be necessary. However, bio_release_page()
> can do one or the other on the basis of BIO_PAGE_PINNED being specified. So
> in my patch I would end up with:
>
> static void bio_release_page(struct bio *bio, struct page *page)
> {
> if (bio->bi_flags & BIO_NO_PAGE_REF)
> ;
> else if (bio->bi_flags & BIO_PAGE_PINNED)
> unpin_user_page(page);
> else
> put_page(page);
> }
Let's please make this a bit more readable with:
static void bio_release_page(struct bio *bio, struct page *page)
{
if (bio->bi_flags & BIO_NO_PAGE_REF)
return;
if (bio->bi_flags & BIO_PAGE_PINNED)
unpin_user_page(page);
else
put_page(page);
}
--
Jens Axboe
next prev parent reply other threads:[~2023-01-09 21:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 0:33 [PATCH v4 0/7] iov_iter: Add extraction helpers David Howells
2023-01-07 0:33 ` [PATCH v4 1/7] iov_iter: Change the direction macros into an enum David Howells
2023-01-07 0:33 ` [PATCH v4 2/7] iov_iter: Use the direction in the iterator functions David Howells
2023-01-07 0:33 ` [PATCH v4 3/7] iov_iter: Use IOCB/IOMAP_WRITE if available rather than iterator direction David Howells
2023-01-07 0:33 ` [PATCH v4 4/7] iov_iter: Add a function to extract a page list from an iterator David Howells
2023-01-07 0:34 ` [PATCH v4 5/7] netfs: Add a function to extract a UBUF or IOVEC into a BVEC iterator David Howells
2023-01-07 0:34 ` [PATCH v4 6/7] netfs: Add a function to extract an iterator into a scatterlist David Howells
2023-01-07 0:34 ` [PATCH v4 7/7] iov_iter, block: Make bio structs pin pages rather than ref'ing if appropriate David Howells
2023-01-09 3:54 ` Jens Axboe
2023-01-09 9:43 ` David Howells
2023-01-09 17:25 ` Jan Kara
2023-01-09 17:27 ` Jens Axboe
2023-01-10 14:42 ` David Howells
2023-01-11 9:58 ` Jan Kara
2023-01-09 17:35 ` Jan Kara
2023-01-09 21:37 ` David Howells
2023-01-09 21:57 ` Jens Axboe [this message]
2023-01-09 22:24 ` David Howells
2023-01-09 22:57 ` Jens Axboe
2023-01-10 14:37 ` David Howells
2023-01-10 21:41 ` Jens Axboe
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=d0bb04e7-7e58-d494-0e39-6e98f3368a7b@kernel.dk \
--to=axboe@kernel.dk \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--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).