mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Matthew Wilcox <mawilcox@microsoft.com>
Subject: Re: [PATCH 0/3] Bitmap optimisations
Date: Wed, 07 Jun 2017 23:37:48 +0200	[thread overview]
Message-ID: <877f0nbhsj.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <20170607142924.28552-1-willy@infradead.org> (Matthew Wilcox's message of "Wed, 7 Jun 2017 07:29:21 -0700")

On Wed, Jun 07 2017, Matthew Wilcox <willy@infradead.org> wrote:

> 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.
>

With the pointer arithmetic fixed,

Acked-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>

      parent reply	other threads:[~2017-06-07 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 14:29 Matthew Wilcox
2017-06-07 14:29 ` [PATCH 1/3] bitmap: Optimise bitmap_set and bitmap_clear of a single bit Matthew Wilcox
2017-06-07 14:29 ` [PATCH 2/3] Turn bitmap_set and bitmap_clear into memset when possible Matthew Wilcox
2017-06-07 21:16   ` Rasmus Villemoes
2017-06-27  7:02     ` Matthew Wilcox
2017-06-27  7:58       ` Rasmus Villemoes
2017-06-07 14:29 ` [PATCH 3/3] bitmap: Use memcmp optimisation in more situations Matthew Wilcox
2017-06-08  1:48   ` Andy Shevchenko
2017-06-08  2:55     ` Matthew Wilcox
2017-06-08 12:31       ` Andy Shevchenko
2017-06-08 13:43         ` Rasmus Villemoes
2017-06-08 14:47           ` Andy Shevchenko
2017-06-07 21:37 ` Rasmus Villemoes [this message]

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=877f0nbhsj.fsf@rasmusvillemoes.dk \
    --to=linux@rasmusvillemoes.dk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=willy@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

all inboxes | Powered by JetHome®