Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Hillf Danton <hdanton@xxxxxxxx>
Subject: Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
From: Xing Zhengjun <zhengjun.xing@xxxxxxxxxxxxxxx>
Date: Fri, 23 Apr 2021 14:55:46 +0800
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, ying.huang@xxxxxxxxx, tim.c.chen@xxxxxxxxxxxxxxx, Shakeel Butt <shakeelb@xxxxxxxxxx>, Michal Hocko <mhocko@xxxxxxxx>, yuzhao@xxxxxxxxxx, wfg@xxxxxxxxxxxxxxxx
In-reply-to: <20210422102325.1332-1-hdanton@sina.com>
References: <20210416023536.168632-1-zhengjun.xing@linux.intel.com> <20210422102325.1332-1-hdanton@sina.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0



On 4/22/2021 6:23 PM, Hillf Danton wrote:

Another option seems like we take a nap at the second time of lru tmi
with some allocators in your case served without the 100ms delay.


Thanks, I will try it with my test cases.

--
Zhengjun Xing

References:
- [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
  - From: zhengjun . xing
- Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
  - From: Hillf Danton

Prev by Date: Re: [PATCH v8] RISC-V: enable XIP
Next by Date: Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
Previous by thread: Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
Next by thread: Re: [RFC] mm/vmscan.c: avoid possible long latency caused by too_many_isolated()
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux