linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>,
	David Howells <dhowells@redhat.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	willy@infradead.org, linux-mm@kvack.org,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Subject: Re: Does GUP page unpinning have to be done in the pinning context?
Date: Thu, 10 Apr 2025 00:28:41 -0700	[thread overview]
Message-ID: <Z_dzKUp1ukaArcSx@infradead.org> (raw)
In-Reply-To: <f04289cd-128a-492e-a692-6f760e2271e2@nvidia.com>

On Wed, Apr 09, 2025 at 07:56:07PM -0700, John Hubbard wrote:
> This topic always worries me, because the original problem with
> dirty pages is still unfixed: setting pages dirty upon unpinning
> is both widely done (last time I checked), and yet broken, because
> it doesn't do a mkdirty() call to set up writeback buffers.
> 
> The solution always seemed to point toward "get a file lease on that
> range, before pinning", but it's a contentious design area to say
> the least.

For the bio based direct I/O implementations we do set the pages
dirty before starting I/O using bio_set_pages_dirty, which uses
folio_mark_dirty and thus calls into the file systems using
->dirty_folio.  But we also do a second pass on I/O completion
before the buffers are unpinned.  Which I think now that we pin
the folios is superfluous.



  reply	other threads:[~2025-04-10  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 10:20 David Howells
2025-04-04 10:29 ` David Hildenbrand
2025-04-04 16:59   ` John Hubbard
2025-04-07  6:39     ` Christoph Hellwig
2025-04-10  2:56       ` John Hubbard
2025-04-10  7:28         ` Christoph Hellwig [this message]
2025-04-10 19:11           ` John Hubbard
2025-04-10 19:14             ` Matthew Wilcox
2025-04-10 19:34               ` John Hubbard
2025-05-12  6:21             ` Christoph Hellwig

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=Z_dzKUp1ukaArcSx@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=david@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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