From: Yu-Jen Chang <arthurchang09@gmail.com>
To: ak@linux.intel.com, jdike@linux.intel.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, richard@nod.at,
anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
linux-um@lists.infradead.org, jserv@ccns.ncku.edu.tw,
Yu-Jen Chang <arthurchang09@gmail.com>
Subject: [PATCH 2/2] x86/um: Use x86_64-optimized memchr
Date: Sat, 28 May 2022 16:12:36 +0800 [thread overview]
Message-ID: <20220528081236.3020-3-arthurchang09@gmail.com> (raw)
In-Reply-To: <20220528081236.3020-1-arthurchang09@gmail.com>
Add x86_64-optimized memchr, which is 4x faster
than the original implementation, into um.
Signed-off-by: Yu-Jen Chang <arthurchang09@gmail.com>
Signed-off-by: Ching-Chun (Jim) Huang <jserv@ccns.ncku.edu.tw>
---
arch/x86/um/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/um/Makefile b/arch/x86/um/Makefile
index ba5789c35..52b7c21ca 100644
--- a/arch/x86/um/Makefile
+++ b/arch/x86/um/Makefile
@@ -28,7 +28,7 @@ else
obj-y += syscalls_64.o vdso/
-subarch-y = ../lib/csum-partial_64.o ../lib/memcpy_64.o ../entry/thunk_64.o
+subarch-y = ../lib/csum-partial_64.o ../lib/memcpy_64.o ../lib/string_64.o ../entry/thunk_64.o
endif
--
2.25.1
next prev parent reply other threads:[~2022-05-28 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 8:12 [PATCH 0/2] x86: Optimize memchr() for x86-64 Yu-Jen Chang
2022-05-28 8:12 ` [PATCH 1/2] x86/lib: Optimize memchr() Yu-Jen Chang
2022-05-28 16:41 ` Tao Zhou
2022-05-29 12:05 ` arthur chang arthur
2022-05-30 8:09 ` David Laight
2022-06-01 5:58 ` Yu-Jen Chang
2022-06-01 8:25 ` David Laight
2022-06-06 3:25 ` Yu-Jen Chang
2022-05-28 8:12 ` Yu-Jen Chang [this message]
2022-05-29 1:10 ` [PATCH 0/2] x86: Optimize memchr() for x86-64 Andi Kleen
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=20220528081236.3020-3-arthurchang09@gmail.com \
--to=arthurchang09@gmail.com \
--cc=ak@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jdike@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=jserv@ccns.ncku.edu.tw \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).