From: Barry Song <21cnbao@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
akpm@linux-foundation.org, ddstreet@ieee.org,
sjenning@redhat.com, vitaly.wool@konsulko.com,
linux-crypto@vger.kernel.org
Cc: chriscli@google.com, chrisl@kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nphamcs@gmail.com, yosryahmed@google.com,
zhouchengming@bytedance.com, Barry Song <v-songbaohua@oppo.com>
Subject: [PATCH 0/3] mm/zswap & crypto/acompress: remove a couple of memcpy
Date: Wed, 3 Jan 2024 22:50:03 +1300 [thread overview]
Message-ID: <20240103095006.608744-1-21cnbao@gmail.com> (raw)
From: Barry Song <v-songbaohua@oppo.com>
The patchset removes a couple of memcpy in zswap and crypto
to improve zswap's performance.
Thanks for Chengming Zhou's test and perf data.
Quote from Chengming,
I just tested these three patches on my server, found improvement in the
kernel build testcase on a tmpfs with zswap (lz4 + zsmalloc) enabled.
mm-stable 501a06fe8e4c patched
real 1m38.028s 1m32.317s
user 19m11.482s 18m39.439s
sys 19m26.445s 17m5.646s
The patchset is based on mm-stable.
Barry Song (3):
crypto: introduce acomp_is_async to expose if a acomp has a scomp
backend
mm/zswap: remove the memcpy if acomp is not asynchronous
crypto: scompress: remove memcpy if sg_nents is 1
crypto/acompress.c | 8 ++++++++
crypto/scompress.c | 35 ++++++++++++++++++++++++++++-------
include/crypto/acompress.h | 9 +++++++++
mm/zswap.c | 6 ++++--
4 files changed, 49 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2024-01-03 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 9:50 Barry Song [this message]
2024-01-03 9:50 ` [PATCH 1/3] crypto: introduce acomp_is_async to expose if a acomp has a scomp backend Barry Song
2024-01-08 22:35 ` Yosry Ahmed
2024-01-09 3:38 ` Barry Song
2024-01-03 9:50 ` [PATCH 2/3] mm/zswap: remove the memcpy if acomp is not asynchronous Barry Song
2024-01-04 0:38 ` Nhat Pham
2024-02-16 3:55 ` Barry Song
2024-01-08 22:36 ` Yosry Ahmed
2024-01-03 9:50 ` [PATCH 3/3] crypto: scompress: remove memcpy if sg_nents is 1 Barry Song
2024-01-25 9:58 ` Herbert Xu
2024-02-16 3:49 ` Barry Song
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=20240103095006.608744-1-21cnbao@gmail.com \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chriscli@google.com \
--cc=chrisl@kernel.org \
--cc=davem@davemloft.net \
--cc=ddstreet@ieee.org \
--cc=hannes@cmpxchg.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=sjenning@redhat.com \
--cc=v-songbaohua@oppo.com \
--cc=vitaly.wool@konsulko.com \
--cc=yosryahmed@google.com \
--cc=zhouchengming@bytedance.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