Hi David,
> >> I think it makes sense to have a generic (non-GUP) version of
> >> check_and_migrate_movable_pages() available in migration.h that
> >> drivers can use to ensure that they don't break memory hotunplug
> >> accidentally.
> >
> > Definately not.
> >
> > Either use the VMA and
I think it makes sense to have a generic (non-GUP) version of
check_and_migrate_movable_pages() available in migration.h that
drivers can use to ensure that they don't break memory hotunplug
accidentally.
Definately not.
Either use the VMA and pin_user_pages(), or implement
pin_user_pages_fd()
On Sun, Aug 27, 2023 at 07:05:59PM +, Kasireddy, Vivek wrote:
> Hi Jason, David,
>
> > > > Sure, we can simply always fail when we detect ZONE_MOVABLE or
> > > MIGRATE_CMA.
> > > > Maybe that keeps at least some use cases working.
> > >
> > > That seems fairly reasonable
> > AFAICS, failing
Hi Jason, David,
> > > Sure, we can simply always fail when we detect ZONE_MOVABLE or
> > MIGRATE_CMA.
> > > Maybe that keeps at least some use cases working.
> >
> > That seems fairly reasonable
> AFAICS, failing udmabuf_create() if we detect one or more pages are in
> ZONE_MOVABLE or
Hi Jason, David,
>
> > Sure, we can simply always fail when we detect ZONE_MOVABLE or
> MIGRATE_CMA.
> > Maybe that keeps at least some use cases working.
>
> That seems fairly reasonable
AFAICS, failing udmabuf_create() if we detect one or more pages are in
ZONE_MOVABLE or MIGRATE_CMA would
On Thu, Aug 24, 2023 at 08:33:09PM +0200, David Hildenbrand wrote:
> Sure, we can simply always fail when we detect ZONE_MOVABLE or MIGRATE_CMA.
> Maybe that keeps at least some use cases working.
That seems fairly reasonable
Jason
On 24.08.23 20:30, Jason Gunthorpe wrote:
On Thu, Aug 24, 2023 at 08:30:17PM +0200, David Hildenbrand wrote:
On 24.08.23 08:31, Kasireddy, Vivek wrote:
Hi David,
- Add a new API to the backing store/allocator to longterm-pin the page.
For example, something along the lines of
On Thu, Aug 24, 2023 at 08:30:17PM +0200, David Hildenbrand wrote:
> On 24.08.23 08:31, Kasireddy, Vivek wrote:
> > Hi David,
> >
> > >
> > > > > - Add a new API to the backing store/allocator to longterm-pin the
> > > > > page.
> > > > > For example, something along the lines of
> > >
On 24.08.23 08:31, Kasireddy, Vivek wrote:
Hi David,
- Add a new API to the backing store/allocator to longterm-pin the page.
For example, something along the lines of
shmem_pin_mapping_page_longterm()
for shmem as suggested by Daniel. A similar one needs to be added for
Hi David,
>
> >> - Add a new API to the backing store/allocator to longterm-pin the page.
> >>For example, something along the lines of
> shmem_pin_mapping_page_longterm()
> >>for shmem as suggested by Daniel. A similar one needs to be added for
> >>hugetlbfs as well.
> >
> > This
- Add a new API to the backing store/allocator to longterm-pin the page.
For example, something along the lines of shmem_pin_mapping_page_longterm()
for shmem as suggested by Daniel. A similar one needs to be added for
hugetlbfs as well.
This may also be reasonable.
Sounds reasonable
On Tue, Aug 22, 2023 at 05:36:56AM +, Kasireddy, Vivek wrote:
> Hi Jason,
>
> > > This patch series adds support for migrating pages associated with
> > > a udmabuf out of the movable zone or CMA to avoid breaking features
> > > such as memory hotunplug.
> > >
> > > The first patch exports
Hi Jason,
> > This patch series adds support for migrating pages associated with
> > a udmabuf out of the movable zone or CMA to avoid breaking features
> > such as memory hotunplug.
> >
> > The first patch exports check_and_migrate_movable_pages() function
> > out of GUP so that the udmabuf
On Wed, Aug 16, 2023 at 11:49:31PM -0700, Vivek Kasireddy wrote:
> This patch series adds support for migrating pages associated with
> a udmabuf out of the movable zone or CMA to avoid breaking features
> such as memory hotunplug.
>
> The first patch exports check_and_migrate_movable_pages()
14 matches
Mail list logo
