From: Jaewon Kim <jaewon31.kim@gmail.com>
To: zhaoyang.huang@unisoc.com, jhubbard@nvidia.com, david@redhat.com
Cc: surenb@google.com, linux-mm@kvack.org
Subject: [RFC] pin_user_pages_fast failure count increased
Date: Tue, 29 Apr 2025 00:17:02 +0900 [thread overview]
Message-ID: <CAJrd-UuAZ6oLLUKnOkTQjKYxSwtPk5noaUFrnNantM7yFiRVuw@mail.gmail.com> (raw)
Hi
If pin_user_pages_fast does not pin all the requested number of pages,
then drivers calling to pin_user_pages_fast should retry until the gup
pins all?
Our GPU driver uses pin_user_pages_fast.
After the recent kernel update, pin_user_pages_fast sometimes does not
pin all the pages, nr_pinned < nr_pages.
I think the following patch affected the pin_user_pages_fast behavior.
1aaf8c122918 mm: gup: fix infinite loop within __get_longterm_locked
BR
Jaewon Kim
next reply other threads:[~2025-04-28 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 15:17 Jaewon Kim [this message]
2025-04-28 15:21 ` David Hildenbrand
2025-04-28 20:14 ` John Hubbard
2025-04-28 20:56 ` David Hildenbrand
2025-04-28 21:12 ` John Hubbard
[not found] ` <CGME20250522092944epcas2p1ca46168564555aad6d9880bda26ec8de@epcas2p1.samsung.com>
2025-05-22 9:27 ` Hyesoo Yu
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=CAJrd-UuAZ6oLLUKnOkTQjKYxSwtPk5noaUFrnNantM7yFiRVuw@mail.gmail.com \
--to=jaewon31.kim@gmail.com \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=zhaoyang.huang@unisoc.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