[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a869aff64f69bd1e1318653559f4c32e9f0a4c08.camel@linux.intel.com>
Date: Tue, 06 Feb 2024 17:08:00 -0800
From: Tim Chen <tim.c.chen@...ux.intel.com>
To: Chris Li <chrisl@...nel.org>
Cc: "Huang, Ying" <ying.huang@...el.com>, Andrew Morton
<akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Wei Xu <weixugc@...gle.com>, Yu
Zhao <yuzhao@...gle.com>, Greg Thelen
<gthelen@...gle.com>, Chun-Tse Shao <ctshao@...gle.com>, Suren
Baghdasaryan <surenb@...gle.com>, Yosry
Ahmed <yosryahmed@...gle.com>, Brain Geffon
<bgeffon@...gle.com>, Minchan Kim <minchan@...nel.org>, Michal Hocko
<mhocko@...e.com>, Mel Gorman <mgorman@...hsingularity.net>, Nhat Pham
<nphamcs@...il.com>, Johannes Weiner <hannes@...xchg.org>, Kairui Song
<kasong@...cent.com>, Zhongkun He <hezhongkun.hzk@...edance.com>, Kemeng
Shi <shikemeng@...weicloud.com>, Barry Song <v-songbaohua@...o.com>
Subject: Re: [PATCH v2] mm: swap: async free swap slot cache entries
On Mon, 2024-02-05 at 11:10 -0800, Chris Li wrote:
>
>
> In our system, a really heavy swap load is rare and it means something
> is already wrong. At that point the app's SLO is likely at risk,
> regardless of long tail swap latency. It is already too late to
> address it at the swap fault end. We need to address the source of the
> problem which is swapping out too much.
>
>
Could some usage scenarios put more pressure on swap than your
usage scenario? Say system with limited RAM and rely on zswap?
Tim
Powered by blists - more mailing lists