From: Andrew Morton <akpm@linux-foundation.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
970639@bugs.debian.org, Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Vitaly Wool <vitaly.wool@konsulko.com>
Subject: Re: ZSWAP still considered experimental?
Date: Tue, 31 May 2022 09:39:27 -0700 [thread overview]
Message-ID: <20220531093927.2292b3defaf9b8cf431ca369@linux-foundation.org> (raw)
In-Reply-To: <10087857.nUPlyArG6x@bagend>
On Tue, 31 May 2022 10:41:05 +0200 Diederik de Haas <didi.debian@cknow.org> wrote:
> In https://bugs.debian.org/970639 the request was made to enable ZSWAP.
>
> Upon it was (rightly) noted that zswap.rst contained this:
> > Zswap is a new feature as of v3.11 and interacts heavily with memory
> > reclaim. This interaction has not been fully explored on the large set
> > of potential configurations and workloads that exist. For this reason,
> > zswap is a work in progress and should be considered experimental.
>
> Furthermore the mm/Kconfig contains this on the ZSWAP option:
> > Compressed cache for swap pages (EXPERIMENTAL)
>
> But the contents of that zswap.rst hasn't changed since the initial commit
> 61b0d76017a50c263c303fa263b295b04e0c68f6 from 2013-07-11.
>
> Similarly, that line in Kconfig hasn't changed either since the initial commit
> 2b2811178e85553405b86e3fe78357b9b95889ce from 2013-07-11.
>
> Should ZSWAP should still be considered experimental or not?
I'd say "not".
prev parent reply other threads:[~2022-05-31 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 8:41 Diederik de Haas
2022-05-31 16:39 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220531093927.2292b3defaf9b8cf431ca369@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=970639@bugs.debian.org \
--cc=ddstreet@ieee.org \
--cc=didi.debian@cknow.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
--cc=vitaly.wool@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox