From: Kees Cook <keescook@chromium.org>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: linux-kernel@vger.kernel.org,
Nick Terrell <nickrterrell@gmail.com>,
Nick Terrell <terrelln@fb.com>,
Norbert Lange <nolange79@gmail.com>, Chris Mason <clm@fb.com>,
linux-kbuild@vger.kernel.org, x86@kernel.org,
gregkh@linuxfoundation.org, Petr Malat <oss@malat.biz>,
Kernel Team <Kernel-team@fb.com>,
Adam Borowski <kilobyte@angband.pl>,
Patrick Williams <patrickw3@fb.com>,
rmikey@fb.com, mingo@kernel.org,
Patrick Williams <patrick@stwcx.xyz>,
Sedat Dilek <sedat.dilek@gmail.com>
Subject: Re: Kernel compression benchmarks
Date: Thu, 2 Jul 2020 08:18:45 -0700 [thread overview]
Message-ID: <202007020818.87EA89106@keescook> (raw)
In-Reply-To: <1588791882.08g1378g67.none@localhost>
On Wed, Jul 01, 2020 at 10:35:48AM -0400, Alex Xu (Hello71) wrote:
> ZSTD compression patches have been sent in a number of times over the
> past few years. Every time, someone asks for benchmarks. Every time,
> someone is concerned about compression time. Sometimes, someone provides
> benchmarks.
Where's the latest series for this, btw? I thought it had landed. :P It
seemed like it was done.
--
Kees Cook
next prev parent reply other threads:[~2020-07-02 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1588791882.08g1378g67.none.ref@localhost>
2020-07-01 14:35 ` Kernel compression benchmarks Alex Xu (Hello71)
2020-07-01 15:50 ` Gao Xiang
2020-07-01 17:32 ` Alex Xu (Hello71)
2020-07-02 15:18 ` Kees Cook [this message]
2020-07-03 8:15 ` Sedat Dilek
2020-07-03 16:06 ` Kees Cook
2020-07-03 17:36 ` Norbert Lange
2020-07-06 15:05 ` Nick Terrell
2020-07-26 16:43 Jan Ziak
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=202007020818.87EA89106@keescook \
--to=keescook@chromium.org \
--cc=Kernel-team@fb.com \
--cc=alex_y_xu@yahoo.ca \
--cc=clm@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nickrterrell@gmail.com \
--cc=nolange79@gmail.com \
--cc=oss@malat.biz \
--cc=patrick@stwcx.xyz \
--cc=patrickw3@fb.com \
--cc=rmikey@fb.com \
--cc=sedat.dilek@gmail.com \
--cc=terrelln@fb.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.