linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md/raid1:!conf->r1buf_pool is unlikely in function   sync_request.
Date: Mon, 2 Apr 2012 11:00:25 +1000	[thread overview]
Message-ID: <20120402110025.3b2a112f@notabene.brown> (raw)
In-Reply-To: <201203281924252189178@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

On Wed, 28 Mar 2012 19:24:29 +0800 "majianpeng" <majianpeng@gmail.com> wrote:

> >From 7f9446682f64e28106dd52cd12bdf74a19fb4015 Mon Sep 17 00:00:00 2001
> From: majianpeng <majianpeng@gmail.com>
> Date: Wed, 28 Mar 2012 19:20:07 +0800
> Subject: [PATCH] md/raid1:!conf->r1buf_pool is unlikely in function
>  sync_request.
> 
> 
> Signed-off-by: majianpeng <majianpeng@gmail.com>
> ---
>  drivers/md/raid1.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
> index 4a40a20..943b3b3 100644
> --- a/drivers/md/raid1.c
> +++ b/drivers/md/raid1.c
> @@ -2246,7 +2246,7 @@ static sector_t sync_request(struct mddev *mddev, sector_t sector_nr, int *skipp
>  	int good_sectors = RESYNC_SECTORS;
>  	int min_bad = 0; /* number of sectors that are bad in all devices */
>  
> -	if (!conf->r1buf_pool)
> +	if (unlikely(!conf->r1buf_pool))
>  		if (init_resync(conf))
>  			return 0;
>  

Hi,
 I'm really happy that you are reviewing the md patches and even finding some
 bugs.  However I find the stream of occasional tiny patches somewhat
 distracting.

 Also I find micro-optimisation like this fairly pointless.  You should only
 really use unlikely() when it will make a real difference to performance,
 and this change won't

 So I won't apply this patch.
 I'll keep looking though the others you have sent since but in future I
 would prefer it if you collected together little patches like this and send
 them as a group.

 If and when you find genuine bugs, feel free to send them straight away.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-04-02  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 11:24 md/raid1:!conf->r1buf_pool is unlikely in function sync_request majianpeng
2012-04-02  1:00 ` NeilBrown [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=20120402110025.3b2a112f@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=majianpeng@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 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).