From: Feng Kan <fkan@apm.com>
To: patches@apm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
philipp.tomsich@theobroma-systems.com,
dann.frazier@canonical.com, tim.gardner@canonical.com,
craig.magina@canonical.com, soni.trilok.oss@gmail.com
Cc: Feng Kan <fkan@apm.com>
Subject: [PATCH V5 0/2] copy to/in/from user optimization
Date: Wed, 23 Sep 2015 11:55:37 -0700 [thread overview]
Message-ID: <1443034539-1848-1-git-send-email-fkan@apm.com> (raw)
This coverts all copy in/from/to user file to use the copy template file.
The copy template file is based on the memcpy.S. The first patch converts
the memcpy to use the copy template as well. Overnight trinity test and
10G iperf was used to test correctness and performance. Noticeable
iperf improvement (~30%) on the receive side.
V5 Changes:
1. Switch patch ordering.
2. Simplify assembly code and use fixed large tags in marco
3. Fixed indentation issue.
Feng Kan (2):
arm64: Change memcpy in kernel to use the copy template file
arm64: copy_to-from-in_user optimization using copy template
arch/arm64/lib/copy_from_user.S | 78 +++++++++-------
arch/arm64/lib/copy_in_user.S | 67 ++++++++------
arch/arm64/lib/copy_template.S | 195 ++++++++++++++++++++++++++++++++++++++++
arch/arm64/lib/copy_to_user.S | 67 ++++++++------
arch/arm64/lib/memcpy.S | 179 ++++++------------------------------
5 files changed, 341 insertions(+), 245 deletions(-)
create mode 100644 arch/arm64/lib/copy_template.S
--
1.9.1
next reply other threads:[~2015-09-23 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 18:55 Feng Kan [this message]
2015-09-23 18:55 ` [PATCH V5 1/2] arm64: Change memcpy in kernel to use the copy template file Feng Kan
2015-09-23 18:55 ` [PATCH V5 2/2] arm64: copy_to-from-in_user optimization using copy template Feng Kan
2015-10-06 15:37 ` [PATCH V5 0/2] copy to/in/from user optimization Catalin Marinas
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=1443034539-1848-1-git-send-email-fkan@apm.com \
--to=fkan@apm.com \
--cc=craig.magina@canonical.com \
--cc=dann.frazier@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@apm.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=soni.trilok.oss@gmail.com \
--cc=tim.gardner@canonical.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
all inboxes | Powered by JetHome®