From: Jonathan Corbet <corbet@lwn.net>
To: David Heidelberg <david@ixit.cz>
Cc: ~okias/devicetree@lists.sr.ht, David Heidelberg <david@ixit.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Docs/admin-guide/mm/zswap: remove a paragraph about zswap being a new feature
Date: Wed, 09 Nov 2022 13:57:31 -0700 [thread overview]
Message-ID: <877d03kfr8.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221104122612.14906-1-david@ixit.cz>
David Heidelberg <david@ixit.cz> writes:
> Nine years have passed since Linux 3.11.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> Documentation/admin-guide/mm/zswap.rst | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/Documentation/admin-guide/mm/zswap.rst b/Documentation/admin-guide/mm/zswap.rst
> index 6e6f7b0d6562..f67de481c7f6 100644
> --- a/Documentation/admin-guide/mm/zswap.rst
> +++ b/Documentation/admin-guide/mm/zswap.rst
> @@ -14,13 +14,7 @@ for potentially reduced swap I/O. This trade-off can also result in a
> significant performance improvement if reads from the compressed cache are
> faster than reads from a swap device.
>
> -.. note::
> - 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.
> -
> - Some potential benefits:
> +Some potential benefits:
>
Applied, thanks.
jon
prev parent reply other threads:[~2022-11-09 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 12:26 [PATCH] Docs/admin-guide/mm/zswap: remove a paragraph about zswap being a new feature David Heidelberg
2022-11-09 20:57 ` Jonathan Corbet [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=877d03kfr8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=david@ixit.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=~okias/devicetree@lists.sr.ht \
/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