From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Implement word-at-a-time string functions for ARM
Date: Fri, 15 Jun 2012 17:22:35 +0100 [thread overview]
Message-ID: <1339777357-32479-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
This is version 2 of the patches originally posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-June/103290.html
There are only cosmetic changes from v1:
- Added Nico's reviewed-by tags
- Removed RFC prefix
- Fixed changelog to echo the fact that we may use clz
I'm still interested in any pathname-heavy benchmarks that people may
have to stress the name hashing code. My simple find test does show an
improvement but I don't know how realistic that is.
Cheers,
Will
Will Deacon (2):
ARM: use generic strnlen_user and strncpy_from_user functions
ARM: dcache: select DCACHE_WORD_ACCESS for little-endian ARMv6+ CPUs
arch/arm/Kconfig | 3 +
arch/arm/include/asm/uaccess.h | 27 ++-------
arch/arm/include/asm/word-at-a-time.h | 96 +++++++++++++++++++++++++++++++++
arch/arm/kernel/armksyms.c | 4 --
arch/arm/lib/Makefile | 1 -
arch/arm/lib/strncpy_from_user.S | 43 ---------------
arch/arm/lib/strnlen_user.S | 40 --------------
7 files changed, 105 insertions(+), 109 deletions(-)
create mode 100644 arch/arm/include/asm/word-at-a-time.h
delete mode 100644 arch/arm/lib/strncpy_from_user.S
delete mode 100644 arch/arm/lib/strnlen_user.S
--
1.7.4.1
next reply other threads:[~2012-06-15 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 16:22 Will Deacon [this message]
2012-06-15 16:22 ` [PATCH v2 1/2] ARM: use generic strnlen_user and strncpy_from_user functions Will Deacon
2012-06-15 16:22 ` [PATCH v2 2/2] ARM: dcache: select DCACHE_WORD_ACCESS for little-endian ARMv6+ CPUs Will Deacon
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=1339777357-32479-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).