From: Kees Cook <keescook@chromium.org>
To: Arvind Sankar <nivedita@alum.mit.edu>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Nick Terrell <nickrterrell@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yann Collet <yann.collet.73@gmail.com>,
Gao Xiang <xiang@kernel.org>,
Sven Schmidt <4sschmid@informatik.uni-hamburg.de>
Subject: Re: [PATCH 1/1] x86/boot/compressed: Use builtin mem functions for decompressor
Date: Wed, 19 Aug 2020 11:14:34 -0700 [thread overview]
Message-ID: <202008191111.4244B09D26@keescook> (raw)
In-Reply-To: <20200804234817.3922187-2-nivedita@alum.mit.edu>
On Tue, Aug 04, 2020 at 07:48:17PM -0400, Arvind Sankar wrote:
> Since commits
>
> c041b5ad8640 ("x86, boot: Create a separate string.h file to provide standard string functions")
> fb4cac573ef6 ("x86, boot: Move memcmp() into string.h and string.c")
>
> the decompressor stub has been using the compiler's builtin memcpy,
> memset and memcmp functions, _except_ where it would likely have the
> largest impact, in the decompression code itself.
>
> Remove the #undef's of memcpy and memset in misc.c so that the
> decompressor code also uses the compiler builtins.
>
> The rationale given in the comment doesn't really apply: just because
> some functions use the out-of-line version is no reason to not use the
> builtin version in the rest.
>
> Replace the comment with an explanation of why memzero and memmove are
> being #define'd.
>
> Drop the suggestion to #undef in boot/string.h as well: the out-of-line
> versions are not really optimized versions, they're generic code that's
> good enough for the preboot environment. The compiler will likely
> generate better code for constant-size memcpy/memset/memcmp if it is
> allowed to.
>
> Most decompressors' performance is unchanged, with the exception of LZ4
> and 64-bit ZSTD.
>
> Before After ARCH
> LZ4 73ms 10ms 32
> LZ4 120ms 10ms 64
> ZSTD 90ms 74ms 64
>
> Measurements on QEMU on 2.2GHz Broadwell Xeon, using defconfig kernels.
>
> Decompressor code size has small differences, with the largest being
> that 64-bit ZSTD decreases just over 2k. The largest code size increase
> was on 64-bit XZ, of about 400 bytes.
>
> Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
> Suggested-by: Nick Terrell <nickrterrell@gmail.com>
> Tested-by: Nick Terrell <nickrterrell@gmail.com>
Did anyone pick this up? (Ingo can you snag it, or maybe akpm who took
the LZ4-specific patch already?) This looks sane to me and provides some
surprising performance benefits. :)
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> arch/x86/boot/compressed/misc.c | 7 ++-----
> arch/x86/boot/string.h | 5 +----
> 2 files changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c
> index 39e592d0e0b4..e478e40fbe5a 100644
> --- a/arch/x86/boot/compressed/misc.c
> +++ b/arch/x86/boot/compressed/misc.c
> @@ -30,12 +30,9 @@
> #define STATIC static
>
> /*
> - * Use normal definitions of mem*() from string.c. There are already
> - * included header files which expect a definition of memset() and by
> - * the time we define memset macro, it is too late.
> + * Provide definitions of memzero and memmove as some of the decompressors will
> + * try to define their own functions if these are not defined as macros.
> */
> -#undef memcpy
> -#undef memset
> #define memzero(s, n) memset((s), 0, (n))
> #define memmove memmove
>
> diff --git a/arch/x86/boot/string.h b/arch/x86/boot/string.h
> index 995f7b7ad512..a232da487cd2 100644
> --- a/arch/x86/boot/string.h
> +++ b/arch/x86/boot/string.h
> @@ -11,10 +11,7 @@ void *memcpy(void *dst, const void *src, size_t len);
> void *memset(void *dst, int c, size_t len);
> int memcmp(const void *s1, const void *s2, size_t len);
>
> -/*
> - * Access builtin version by default. If one needs to use optimized version,
> - * do "undef memcpy" in .c file and link against right string.c
> - */
> +/* Access builtin version by default. */
> #define memcpy(d,s,l) __builtin_memcpy(d,s,l)
> #define memset(d,c,l) __builtin_memset(d,c,l)
> #define memcmp __builtin_memcmp
> --
> 2.26.2
>
--
Kees Cook
next prev parent reply other threads:[~2020-08-19 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 19:40 [PATCH] lz4: Fix kernel decompression speed Nick Terrell
2020-08-03 21:57 ` Arvind Sankar
2020-08-03 22:55 ` Nick Terrell
2020-08-04 1:56 ` Arvind Sankar
2020-08-04 2:57 ` Nick Terrell
2020-08-04 15:19 ` Arvind Sankar
2020-08-04 17:59 ` Nick Terrell
2020-08-04 23:48 ` [PATCH 0/1] x86/boot/compressed: Use builtin mem functions for decompressor Arvind Sankar
2020-08-04 23:48 ` [PATCH 1/1] " Arvind Sankar
2020-08-19 18:14 ` Kees Cook [this message]
2020-08-19 18:22 ` Linus Torvalds
2020-08-04 8:32 ` [PATCH] lz4: Fix kernel decompression speed Pavel Machek
2020-08-04 15:16 ` Arvind Sankar
2020-08-04 17:18 ` Nick Terrell
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=202008191111.4244B09D26@keescook \
--to=keescook@chromium.org \
--cc=4sschmid@informatik.uni-hamburg.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nickrterrell@gmail.com \
--cc=nivedita@alum.mit.edu \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xiang@kernel.org \
--cc=yann.collet.73@gmail.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
Powered by JetHome