From: Matthew Wilcox <willy@infradead.org>
To: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] mm/gup.c: Reorganize try_get_folio()
Date: Tue, 13 Jun 2023 21:29:27 +0100 [thread overview]
Message-ID: <ZIjRpy1qBJGOxciw@casper.infradead.org> (raw)
In-Reply-To: <20230613201827.9441-5-vishal.moola@gmail.com>
On Tue, Jun 13, 2023 at 01:18:26PM -0700, Vishal Moola (Oracle) wrote:
> struct folio *try_grab_folio(struct page *page, int refs, unsigned int flags)
> {
> + struct folio *folio;
checkpatch will whinge about there not being a blank line here, and in
this case, I think it's correct.
> if (unlikely(!(flags & FOLL_PCI_P2PDMA) && is_pci_p2pdma_page(page)))
> return NULL;
>
> + folio = try_get_folio(page, refs);
> +
> if (flags & FOLL_GET)
> - return try_get_folio(page, refs);
> - else if (flags & FOLL_PIN) {
> - struct folio *folio;
> + return folio;
>
> - /*
> - * Can't do FOLL_LONGTERM + FOLL_PIN gup fast path if not in a
> - * right zone, so fail and let the caller fall back to the slow
> - * path.
> - */
> - if (unlikely((flags & FOLL_LONGTERM) &&
> - !is_longterm_pinnable_page(page)))
> - return NULL;
> + if (unlikely(!(flags & FOLL_PIN))) {
> + WARN_ON_ONCE(1);
> + return NULL;
Don't we need to folio_put_refs() in this case? Or rather, I think the
if (WARN_ON_ONCE(flags & (FOLL_PIN|FOLL_GET) == 0) {
test should be first.
> + /*
> + * CAUTION: Don't use compound_head() on the page before this
> + * point, the result won't be stable.
> + */
I think we can lose the comment at this point?
> + if (!folio)
> + return NULL;
next prev parent reply other threads:[~2023-06-13 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 20:18 [PATCH 0/5] Replace is_longterm_pinnable_page() Vishal Moola (Oracle)
2023-06-13 20:18 ` [PATCH 1/5] mmzone: Introduce folio_is_zone_movable() Vishal Moola (Oracle)
2023-06-13 20:53 ` Matthew Wilcox
2023-06-13 20:18 ` [PATCH 2/5] mmzone: Introduce folio_migratetype() Vishal Moola (Oracle)
2023-06-13 20:53 ` Matthew Wilcox
2023-06-13 20:18 ` [PATCH 3/5] mm/gup_test.c: Convert verify_dma_pinned() to us folios Vishal Moola (Oracle)
2023-06-13 20:54 ` Matthew Wilcox
2023-06-17 19:29 ` Lorenzo Stoakes
2023-06-13 20:18 ` [PATCH 4/5] mm/gup.c: Reorganize try_get_folio() Vishal Moola (Oracle)
2023-06-13 20:29 ` Matthew Wilcox [this message]
2023-06-13 20:18 ` [PATCH 5/5] mm: Remove is_longterm_pinnable_page() and Reimplement folio_is_longterm_pinnable() Vishal Moola (Oracle)
2023-06-13 20:52 ` Matthew Wilcox
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=ZIjRpy1qBJGOxciw@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vishal.moola@gmail.com \
/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