From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md:Add break if find.
Date: Wed, 14 Mar 2012 13:06:15 +1100 [thread overview]
Message-ID: <20120314130615.7e5dbd42@notabene.brown> (raw)
In-Reply-To: <201203131328071710700@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Tue, 13 Mar 2012 13:28:12 +0800 "majianpeng" <majianpeng@gmail.com> wrote:
> >From 6e04c2374db7fc34ccbf9f37f85e735a349c816c Mon Sep 17 00:00:00 2001
> From: majianpeng <majianpeng@gmail.com>
> Date: Tue, 13 Mar 2012 13:26:25 +0800
> Subject: [PATCH] md:Add break if find.
>
>
> Signed-off-by: majianpeng <majianpeng@gmail.com>
> ---
> drivers/md/raid5.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 360f2b9..e05d9e5 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -4369,8 +4369,10 @@ static inline sector_t sync_request(struct mddev *mddev, sector_t sector_nr, int
> * recovery aborts.
> */
> for (i = 0; i < conf->raid_disks; i++)
> - if (conf->disks[i].rdev == NULL)
> + if (conf->disks[i].rdev == NULL) {
> still_degraded = 1;
> + break;
> + }
>
> bitmap_start_sync(mddev->bitmap, sector_nr, &sync_blocks, still_degraded);
>
Thanks - however I don't think I'll apply this one.
It is a micro optimisation which only improve an uncommon case a little,
but it makes the source code long and the generated machine code longer (by
32 bytes on x86_64).
So I don't really think it is a win.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-03-14 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:28 md:Add break if find majianpeng
2012-03-14 2:06 ` NeilBrown [this message]
2012-03-14 2:30 ` kedacomkernel
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=20120314130615.7e5dbd42@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 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.