mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ferran Duarri <ferran.duarri@me.com>
To: "Christian König" <christian.koenig@amd.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	Ferran Duarri <ferran.duarri@me.com>
Subject: Re: [RFC PATCH] dma-buf: add a generic reclaim-priority hint
Date: Mon, 31 Aug 2026 15:16:46 +0200	[thread overview]
Message-ID: <20260831131648.200687-1-ferran.duarri@me.com> (raw)
In-Reply-To: <5397d2cb-4eb1-461f-82f6-57a1ea5c8499@amd.com>

Thanks, and the FOLL_LONGTERM framing was my error - I should've checked it
before I wrote it. I'd been treating the pin as an accounting detail rather
than the thing that makes the buffer un-migratable, and once you look at
check_and_migrate_movable_pages_or_folios() and what CMA does around it,
that's obviously not a premise to build UAPI on.

On the in-tree user, that's fair. I said much the same in a follow-up on the
20th which you may not have seen - there isn't one, the only consumer is my
own out-of-tree module, and that isn't a reason to take UAPI.

One thing I'd like to understand before dropping it. You mention the
exporter migrating a buffer between local memory, system memory and swap.
If this ever did get an in-tree consumer, is that the shape you'd expect -
something on dma_buf_ops the exporter implements, rather than a hint field
plus an ioctl? I'd rather hear the direction is wrong than come back later
with the same idea in different clothes.

Cheers,
Ferran

      reply	other threads:[~2026-08-31 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 19:08 Ferran Duarri
2026-08-20 19:53 ` Ferran Duarri
2026-08-20 20:04 ` Ferran Duarri
2026-08-25 12:24 ` Christian König
2026-08-31 13:16   ` Ferran Duarri [this message]

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=20260831131648.200687-1-ferran.duarri@me.com \
    --to=ferran.duarri@me.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.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

all inboxes | Powered by JetHome®