On 15 Apr 2021, at 2:45, Huang, Ying wrote:
> "Zi Yan" writes:
>
>> On 13 Apr 2021, at 23:00, Huang, Ying wrote:
>>
>>> Yang Shi writes:
>>>
The generic migration path will check refcount, so no need check refcount
here.
But the old code actually prevents from migrating shared TH
"Zi Yan" writes:
> On 13 Apr 2021, at 23:00, Huang, Ying wrote:
>
>> Yang Shi writes:
>>
>>> The generic migration path will check refcount, so no need check refcount
>>> here.
>>> But the old code actually prevents from migrating shared THP (mapped by
>>> multiple
>>> processes), so bail out
On Tue, Apr 13, 2021 at 8:00 PM Huang, Ying wrote:
>
> Yang Shi writes:
>
> > The generic migration path will check refcount, so no need check refcount
> > here.
> > But the old code actually prevents from migrating shared THP (mapped by
> > multiple
> > processes), so bail out early if mapcoun
On 13 Apr 2021, at 23:00, Huang, Ying wrote:
> Yang Shi writes:
>
>> The generic migration path will check refcount, so no need check refcount
>> here.
>> But the old code actually prevents from migrating shared THP (mapped by
>> multiple
>> processes), so bail out early if mapcount is > 1 to k
Yang Shi writes:
> The generic migration path will check refcount, so no need check refcount
> here.
> But the old code actually prevents from migrating shared THP (mapped by
> multiple
> processes), so bail out early if mapcount is > 1 to keep the behavior.
What prevents us from migrating sha
The generic migration path will check refcount, so no need check refcount here.
But the old code actually prevents from migrating shared THP (mapped by multiple
processes), so bail out early if mapcount is > 1 to keep the behavior.
Signed-off-by: Yang Shi
---
mm/migrate.c | 16
6 matches
Mail list logo
