[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKEwX=NknMShU0jM51LUJC9FO8OROFy-4igo_qR7xQvE8=zu9A@mail.gmail.com>
Date: Fri, 17 Jan 2025 10:09:12 +0700
From: Nhat Pham <nphamcs@...il.com>
To: Yosry Ahmed <yosryahmed@...gle.com>
Cc: lsf-pc@...ts.linux-foundation.org, akpm@...ux-foundation.org,
hannes@...xchg.org, ryncsn@...il.com, chengming.zhou@...ux.dev,
chrisl@...nel.org, linux-mm@...ck.org, kernel-team@...a.com,
linux-kernel@...r.kernel.org, shakeel.butt@...ux.dev, hch@...radead.org,
hughd@...gle.com, 21cnbao@...il.com, usamaarif642@...il.com
Subject: Re: [LSF/MM/BPF TOPIC] Virtual Swap Space
On Fri, Jan 17, 2025 at 9:47 AM Nhat Pham <nphamcs@...il.com> wrote:
>
> No particular reason why we can't squeeze it into swap counts other
> than clarity :) It's going to be a bit annoying working with swap
> count values (swap count increment is now * 2 instead of ++ etc.).
errr.. += 2 I suppose (since the lowest bit is now the swap cache
bit). But point stands I suppose lol.
Getting exact swap count will be swap read then divide by 2 etc.
Powered by blists - more mailing lists