All of lore.kernel.org
 help / color / mirror / Atom feed
From: yalin wang <yalin.wang2010@gmail.com>
To: Jia He <hejianet@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Michal Nazarewicz <mina86@mina86.com>,
	Yury Norov <yury.norov@gmail.com>, Tejun Heo <tj@kernel.org>,
	Martin Kepplinger <martink@posteo.de>,
	George Spelvin <linux@horizon.com>,
	Ingo Molnar <mingo@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 2/3] lib: Introduce 2 bit ops api: all_is_bit_{one,zero}
Date: Thu, 19 Nov 2015 16:49:51 +0800	[thread overview]
Message-ID: <265F6375-198E-4D74-8915-81E3995B7D4D@gmail.com> (raw)
In-Reply-To: <1447915724-29709-3-git-send-email-hejianet@gmail.com>


> On Nov 19, 2015, at 14:48, Jia He <hejianet@gmail.com> wrote:
> 
> 
why not use memcmp() to compare with  0x0000000 or 0xffffffff  ?
memcmp() have better performance on some platforms .

Thanks


  parent reply	other threads:[~2015-11-19  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  6:48 [PATCH v2 0/3] Improve bitmap_empty and bitmap_full Jia He
2015-11-19  6:48 ` [PATCH v2 1/3] linux/bitmap: Move 2 mask macro from bitmap.h to bitops.h Jia He
2015-11-19  6:48 ` [PATCH v2 2/3] lib: Introduce 2 bit ops api: all_is_bit_{one,zero} Jia He
2015-11-19  8:40   ` xinhui
2015-11-19  8:55     ` hejianet
2015-11-19  8:49   ` yalin wang [this message]
2015-11-19  6:48 ` [PATCH v3 3/3] linux/bitmap: Replace find_fisrt_{zero_}bit with the new lightweight api Jia He
2015-11-19  9:01 ` [PATCH v2 0/3] Improve bitmap_empty and bitmap_full Rasmus Villemoes

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=265F6375-198E-4D74-8915-81E3995B7D4D@gmail.com \
    --to=yalin.wang2010@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dvlasenk@redhat.com \
    --cc=hejianet@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=linux@rasmusvillemoes.dk \
    --cc=martink@posteo.de \
    --cc=mina86@mina86.com \
    --cc=mingo@kernel.org \
    --cc=tj@kernel.org \
    --cc=yury.norov@gmail.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.