From: David Hildenbrand <david@redhat.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org
Cc: Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Mike Kravetz <mike.kravetz@oracle.com>,
Hugh Dickins <hughd@google.com>, Peter Xu <peterx@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Dongwon Kim <dongwon.kim@intel.com>,
Junxiao Chang <junxiao.chang@intel.com>
Subject: Re: [PATCH v12 0/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios
Date: Tue, 26 Mar 2024 17:12:49 +0100 [thread overview]
Message-ID: <205e0755-5dc8-45f7-8d9f-59dde9951307@redhat.com> (raw)
In-Reply-To: <20240225080008.1019653-1-vivek.kasireddy@intel.com>
On 25.02.24 08:56, Vivek Kasireddy wrote:
> Currently, some drivers (e.g, Udmabuf) that want to longterm-pin
> the pages/folios associated with a memfd, do so by simply taking a
> reference on them. This is not desirable because the pages/folios
> may reside in Movable zone or CMA block.
>
> Therefore, having drivers use memfd_pin_folios() API ensures that
> the folios are appropriately pinned via FOLL_PIN for longterm DMA.
>
> This patchset also introduces a few helpers and converts the Udmabuf
> driver to use folios and memfd_pin_folios() API to longterm-pin
> the folios for DMA. Two new Udmabuf selftests are also included to
> test the driver and the new API.
>
> ---
Sorry Vivek, I got distracted. What's the state of this? I assume it's
not in an mm tree yet.
I try to get this reviewed this week. If I fail to do that, please ping me.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-03-26 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 7:56 Vivek Kasireddy
2024-02-25 7:56 ` [PATCH v12 1/8] mm/gup: Introduce unpin_folio/unpin_folios helpers Vivek Kasireddy
[not found] ` <54381897-35bc-442d-951d-b9a89f16b1a5@redhat.com>
2024-04-02 14:14 ` David Hildenbrand
2024-02-25 7:56 ` [PATCH v12 2/8] mm/gup: Introduce check_and_migrate_movable_folios() Vivek Kasireddy
2024-04-02 14:26 ` David Hildenbrand
2024-02-25 7:56 ` [PATCH v12 3/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios Vivek Kasireddy
2024-02-25 7:57 ` [PATCH v12 4/8] udmabuf: Use vmf_insert_pfn and VM_PFNMAP for handling mmap Vivek Kasireddy
2024-02-25 7:57 ` [PATCH v12 5/8] udmabuf: Add back support for mapping hugetlb pages Vivek Kasireddy
2024-02-25 7:57 ` [PATCH v12 6/8] udmabuf: Convert udmabuf driver to use folios Vivek Kasireddy
2024-02-25 7:57 ` [PATCH v12 7/8] udmabuf: Pin the pages using memfd_pin_folios() API Vivek Kasireddy
2024-02-25 7:57 ` [PATCH v12 8/8] selftests/udmabuf: Add tests to verify data after page migration Vivek Kasireddy
2024-03-26 16:12 ` David Hildenbrand [this message]
2024-03-29 5:38 ` [PATCH v12 0/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios Kasireddy, Vivek
2024-03-29 11:42 ` David Hildenbrand
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=205e0755-5dc8-45f7-8d9f-59dde9951307@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jgg@nvidia.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 \
--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