From: Jason Gunthorpe <jgg@nvidia.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>
Cc: dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
David Hildenbrand <david@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Mike Kravetz <mike.kravetz@oracle.com>,
Hugh Dickins <hughd@google.com>, Peter Xu <peterx@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Dongwon Kim <dongwon.kim@intel.com>,
Junxiao Chang <junxiao.chang@intel.com>
Subject: Re: [PATCH v1 1/3] mm/gup: Introduce pin_user_pages_fd() for pinning shmem/hugetlbfs file pages
Date: Tue, 10 Oct 2023 10:51:21 -0300 [thread overview]
Message-ID: <20231010135121.GK3952@nvidia.com> (raw)
In-Reply-To: <20231003074447.3245729-2-vivek.kasireddy@intel.com>
On Tue, Oct 03, 2023 at 12:44:45AM -0700, Vivek Kasireddy wrote:
> +/**
> + * pin_user_pages_fd() - pin user pages associated with a file
> + * @fd: the fd whose pages are to be pinned
> + * @start: starting file offset
> + * @nr_pages: number of pages from start to pin
> + * @gup_flags: flags modifying pin behaviour
> + * @pages: array that receives pointers to the pages pinned.
> + * Should be at least nr_pages long.
> + *
> + * Attempt to pin (and migrate) pages associated with a file belonging to
> + * either shmem or hugetlbfs. An error is returned if pages associated with
> + * hugetlbfs files are not present in the page cache. However, shmem pages
> + * are swapped in or allocated if they are not present in the page cache.
> + *
> + * Returns number of pages pinned. This would be equal to the number of
> + * pages requested.
> + * If nr_pages is 0 or negative, returns 0. If no pages were pinned, returns
> + * -errno.
> + */
> +long pin_user_pages_fd(int fd, pgoff_t start, unsigned long nr_pages,
> + unsigned int gup_flags, struct page **pages)
> +{
> + struct page *page;
> + struct file *filep;
> + unsigned int flags, i;
> + long ret;
> +
> + if (nr_pages <= 0)
> + return 0;
> + if (!is_valid_gup_args(pages, NULL, &gup_flags, FOLL_PIN))
> + return 0;
> +
> + if (start < 0)
> + return -EINVAL;
> +
> + filep = fget(fd);
> + if (!filep)
> + return -EINVAL;
I think the caller should pass in the file *
In some cases we will need to hold a reference on it for a long time.
> + if (!shmem_file(filep) && !is_file_hugepages(filep))
> + return -EINVAL;
> +
> + flags = memalloc_pin_save();
> + do {
> + for (i = 0; i < nr_pages; i++) {
> + if (shmem_mapping(filep->f_mapping)) {
> + page = shmem_read_mapping_page(filep->f_mapping,
> + start + i);
> + if (IS_ERR(page)) {
> + ret = PTR_ERR(page);
> + goto err;
> + }
> + } else {
> + page = find_get_page_flags(filep->f_mapping,
> + start + i,
> + FGP_ACCESSED);
> + if (!page) {
> + ret = -EINVAL;
> + goto err;
> + }
I don't know these APIs at all, but I admit to being surprised we need
the special case for shmem ?
> + ret = try_grab_page(page, FOLL_PIN);
> + if (unlikely(ret))
> + goto err;
> +
> + pages[i] = page;
> + put_page(pages[i]);
> + }
> +
> + ret = check_and_migrate_movable_pages(nr_pages, pages);
> + } while (ret == -EAGAIN);
It seems OK, but I do wish it was faster :) Maybe for another day.
Jason
next prev parent reply other threads:[~2023-10-10 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 7:44 [PATCH v1 0/3] " Vivek Kasireddy
2023-10-03 7:44 ` [PATCH v1 1/3] " Vivek Kasireddy
2023-10-06 8:03 ` David Hildenbrand
2023-10-06 18:43 ` Jason Gunthorpe
2023-10-17 7:39 ` Kasireddy, Vivek
2023-10-10 13:51 ` Jason Gunthorpe [this message]
2023-10-03 7:44 ` [PATCH v1 2/3] udmabuf: Pin the pages using pin_user_pages_fd() API Vivek Kasireddy
2023-10-03 7:44 ` [PATCH v1 3/3] selftests/dma-buf/udmabuf: Add tests to verify data after page migration Vivek Kasireddy
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=20231010135121.GK3952@nvidia.com \
--to=jgg@nvidia.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hughd@google.com \
--cc=junxiao.chang@intel.com \
--cc=kraxel@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=peterx@redhat.com \
--cc=vivek.kasireddy@intel.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