All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/3] f2fs: add fast path for find_next_{zero}bit
Date: Fri, 21 Oct 2016 03:35:37 -0700	[thread overview]
Message-ID: <20161021103537.GA14327@infradead.org> (raw)
In-Reply-To: <20161021022847.55629-1-jaegeuk@kernel.org>

On Thu, Oct 20, 2016 at 07:28:45PM -0700, Jaegeuk Kim wrote:
> This patch adds checking the first two bits when searching zero or one bits to
> avoid costly find_next_{zero}bit operations.

Please fix this in the generic iplementations instead of adding your
local workarounds.

      parent reply	other threads:[~2016-10-21 10:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21  2:28 [PATCH 1/3] f2fs: add fast path for find_next_{zero}bit Jaegeuk Kim
2016-10-21  2:28 ` Jaegeuk Kim
2016-10-21  2:28 ` [PATCH 2/3] f2fs: use __set_page_dirty_nobuffers directly Jaegeuk Kim
2016-10-21  2:28   ` Jaegeuk Kim
2016-11-02  7:34   ` [f2fs-dev] " Chao Yu
2016-11-02  7:34     ` Chao Yu
2016-11-02 17:23     ` Jaegeuk Kim
2016-11-02 17:23       ` [f2fs-dev] " Jaegeuk Kim
2016-11-03  9:50       ` Chao Yu
2016-11-03  9:50         ` Chao Yu
2016-11-03 17:57         ` Jaegeuk Kim
2016-11-04 15:51           ` Chao Yu
2016-11-04 15:51             ` [f2fs-dev] " Chao Yu
2016-10-21  2:28 ` [PATCH 3/3] f2fs: remove percpu_count due to performance regression Jaegeuk Kim
2016-10-21 10:35 ` Christoph Hellwig [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=20161021103537.GA14327@infradead.org \
    --to=hch@infradead.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.