[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210816173959.950443c7516a2b178e2ec376@linux-foundation.org>
Date: Mon, 16 Aug 2021 17:39:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
David Hildenbrand <david@...hat.com>,
Michal Hocko <mhocko@...e.com>,
Oscar Salvador <osalvador@...e.de>, Zi Yan <ziy@...dia.com>,
Muchun Song <songmuchun@...edance.com>,
Naoya Horiguchi <naoya.horiguchi@...ux.dev>,
David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH RESEND 0/8] hugetlb: add demote/split page functionality
On Mon, 16 Aug 2021 17:17:50 -0700 Mike Kravetz <mike.kravetz@...cle.com> wrote:
> >
> > And how does one know the operation has completed so the sysfs files
> > can be reloaded for another operation?
> >
>
> When the write to the file is complete, the operation has completed.
> Not exactly sure what you mean by reloading the sysfs files for
> another operation?
If userspace wishes to perform another demote operation, it must wait
for the preceding one to complete.
Presumably if thread A is blocked in a write to `demote' and thread B
concurrently tries to perform a demotion, thread B will be blocked as
well? Was this tested?
Lots of things are to be added to changelogs & documentation, methinks.
Powered by blists - more mailing lists