linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Vivek Kasireddy <vivek.kasireddy@intel.com>,
	 dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
	David Hildenbrand <david@redhat.com>,
	 Matthew Wilcox <willy@infradead.org>,
	Christoph Hellwig <hch@infradead.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	 Hugh Dickins <hughd@google.com>, Peter Xu <peterx@redhat.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	 Dongwon Kim <dongwon.kim@intel.com>,
	Junxiao Chang <junxiao.chang@intel.com>
Subject: Re: [PATCH v14 0/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios
Date: Thu, 23 May 2024 10:28:07 +0200	[thread overview]
Message-ID: <awodz2vwnicscpyoqrp6bqdtgetv3h7wvifdxk4u7bvlczspog@qgy3isyuwkfp> (raw)
In-Reply-To: <CAPM=9tyuX7DKxaQ1zT7b4NYqhnjA3uLHK-kxXgeiubTZcy42=w@mail.gmail.com>

On Thu, May 23, 2024 at 01:13:11PM GMT, Dave Airlie wrote:
> Hey
> 
> Gerd, do you have any time to look at this series again, I think at
> v14 we should probably consider landing it.

Phew.  Didn't follow recent MM changes closely, don't know much about
folios beyond LWN coverage.  The changes look sane to my untrained eye,
I wouldn't rate that a 'review' though.

The patch series structure looks a bit odd, with patch #5 adding hugetlb
support, with the functions added being removed again in patch #7 after
switching to folios.  But maybe regression testing the series is easier
that way ...

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

take care,
  Gerd



  reply	other threads:[~2024-05-23  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  6:59 Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 1/8] mm/gup: Introduce unpin_folio/unpin_folios helpers Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 2/8] mm/gup: Introduce check_and_migrate_movable_folios() Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 3/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 4/8] udmabuf: Use vmf_insert_pfn and VM_PFNMAP for handling mmap Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 5/8] udmabuf: Add back support for mapping hugetlb pages Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 6/8] udmabuf: Convert udmabuf driver to use folios Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 7/8] udmabuf: Pin the pages using memfd_pin_folios() API Vivek Kasireddy
2024-04-11  6:59 ` [PATCH v14 8/8] selftests/udmabuf: Add tests to verify data after page migration Vivek Kasireddy
2024-05-23  3:13 ` [PATCH v14 0/8] mm/gup: Introduce memfd_pin_folios() for pinning memfd folios Dave Airlie
2024-05-23  8:28   ` Gerd Hoffmann [this message]
2024-05-23 23:04     ` Kasireddy, Vivek

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=awodz2vwnicscpyoqrp6bqdtgetv3h7wvifdxk4u7bvlczspog@qgy3isyuwkfp \
    --to=kraxel@redhat.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=david@redhat.com \
    --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=linux-mm@kvack.org \
    --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