From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <simona.vetter@ffwll.ch>,
<felix.kuehling@amd.com>, <apopple@nvidia.com>
Subject: Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns
Date: Wed, 23 Oct 2024 19:22:29 -0700 [thread overview]
Message-ID: <20241023192229.64333482554de0135397cb23@linux-foundation.org> (raw)
In-Reply-To: <Zxmn6uGSOgi11rO2@DUT025-TGLU.fm.intel.com>
On Thu, 24 Oct 2024 01:50:34 +0000 Matthew Brost <matthew.brost@intel.com> wrote:
> > On Wed, 23 Oct 2024 16:39:44 -0700 Matthew Brost <matthew.brost@intel.com> wrote:
> >
> > > Implement migrate_device_pfns to prepare an array of PFNs for migration.
> > > Handles non-contiguous ranges of device pages that require migration.
> >
> > OK, that's "what". We're more interested in "why".
> >
>
> Sure can add. The 'why' is:
>
> A non-contiguous allocation of device pages can occur if a device is
> under memory pressure within a single driver allocation of device
> memory. Additionally, a driver allocation of memory can also be evicted
> under memory pressure. Therefore, an interface for migrating a set of
> non-contiguous device pages is required.
OK, thanks. But when merging a new interface such as this we like to
see the code which will actually use the interface. Along with reasons
to believe that the calling code will actually be merged, so we don't
end up with a new interface which has no callers.
Apart from that, I suspect that it makes more sense to merge this via
the DRM tree, alongside the code which uses it.
prev parent reply other threads:[~2024-10-24 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 23:39 [PATCH v3 0/1] " Matthew Brost
2024-10-23 23:39 ` [PATCH v3 1/1] " Matthew Brost
2024-10-24 1:22 ` Andrew Morton
2024-10-24 1:50 ` Matthew Brost
2024-10-24 2:22 ` Andrew Morton [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=20241023192229.64333482554de0135397cb23@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=simona.vetter@ffwll.ch \
/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