From: Matthew Wilcox <willy@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Matthew Wilcox <mawilcox@microsoft.com>
Subject: [PATCH v2 0/4] Bitmap optimisations
Date: Wed, 28 Jun 2017 08:32:17 -0700 [thread overview]
Message-ID: <20170628153221.11322-1-willy@infradead.org> (raw)
From: Matthew Wilcox <mawilcox@microsoft.com>
These three bitmap patches use more efficient specialisations when the
compiler can figure out that it's safe to do so. Thanks to Rasmus'
eagle eyes, a nasty bug in v1 was avoided, and I've added a test case
which would have caught it.
Matthew Wilcox (4):
test_bitmap: Add optimisation tests
bitmap: Optimise bitmap_set and bitmap_clear of a single bit
Turn bitmap_set and bitmap_clear into memset when possible
bitmap: Use memcmp optimisation in more situations
include/linux/bitmap.h | 33 +++++++++++++++++++++++++++------
lib/bitmap.c | 8 ++++----
lib/test_bitmap.c | 29 +++++++++++++++++++++++++++++
3 files changed, 60 insertions(+), 10 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-28 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 15:32 Matthew Wilcox [this message]
2017-06-28 15:32 ` [PATCH v2 1/4] test_bitmap: Add optimisation tests Matthew Wilcox
2017-06-28 15:32 ` [PATCH v2 2/4] bitmap: Optimise bitmap_set and bitmap_clear of a single bit Matthew Wilcox
2017-06-28 15:32 ` [PATCH v2 3/4] Turn bitmap_set and bitmap_clear into memset when possible Matthew Wilcox
2017-06-28 15:32 ` [PATCH v2 4/4] bitmap: Use memcmp optimisation in more situations Matthew Wilcox
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=20170628153221.11322-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mawilcox@microsoft.com \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.