From: Neil Brown <neilb@suse.de>
To: raz ben yehuda <raziebe@gmail.com>
Cc: linux raid <linux-raid@vger.kernel.org>, ofer <ofer@bitband.com>,
yaron <yaronp@bitband.com>
Subject: Re: Subject: [PATCH 002/009]: have raid0 report its formation
Date: Wed, 20 May 2009 11:27:41 +1000 [thread overview]
Message-ID: <18963.23693.620765.31533@notabene.brown> (raw)
In-Reply-To: message from raz ben yehuda on Tuesday May 19
On Tuesday May 19, raziebe@gmail.com wrote:
> Report to the user what are the raid zones
You didn't reply to my question of:
- why did you want this?
- can it be combined with other information printed by
make_strip_zones?
- if not, can it be combined with the MD_DEBUG part of
raid0_status??
I've applied it for now, but I need answers before I can promise to
keep it.
NeilBrown
>
> raid0.c | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> Signed-off-by: raziebe@gmail.com
> ---
> diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
> index 8049a92..0a6d0fa 100644
> --- a/drivers/md/raid0.c
> +++ b/drivers/md/raid0.c
> @@ -52,6 +52,38 @@ static int raid0_congested(void *data, int bits)
> return ret;
> }
>
> +/*
> + * inform the user of the raid configuration
> +*/
> +static void dump_zones(mddev_t *mddev)
> +{
> + int j, k, h;
> + sector_t zone_size = 0;
> + sector_t zone_start = 0;
> + char b[BDEVNAME_SIZE];
> + raid0_conf_t *conf = mddev->private;
> + printk(KERN_INFO "******* %s configuration *********",
> + mdname(mddev));
> + h = 0;
> + for (j = 0; j < conf->nr_strip_zones; j++) {
> + printk("\nzone%d", j);
> + printk("=[");
> + for (k = 0; k < conf->strip_zone[j].nb_dev; k++)
> + printk("%s/",
> + bdevname(conf->devlist[j*mddev->raid_disks
> + + k]->bdev, b));
> +
> + zone_size = conf->strip_zone[j].zone_end - zone_start;
> + printk("]\n\t zone offset=%llukb "
> + "device offset=%llukb size=%llukb\n",
> + (unsigned long long)zone_start>>1,
> + (unsigned long long)conf->strip_zone[j].dev_start>>1,
> + (unsigned long long)zone_size>>1);
> + zone_start = conf->strip_zone[j].zone_end;
> + }
> + printk(KERN_INFO "**********************************\n\n");
> +}
> +
> static int create_strip_zones(mddev_t *mddev)
> {
> int i, c, j, err;
> @@ -291,6 +323,7 @@ static int raid0_run(mddev_t *mddev)
> }
>
> blk_queue_merge_bvec(mddev->queue, raid0_mergeable_bvec);
> + dump_zones(mddev);
> return 0;
> }
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-20 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 16:06 Subject: [PATCH 002/009]: have raid0 report its formation raz ben yehuda
2009-05-20 1:27 ` Neil Brown [this message]
2009-05-20 13:50 ` raz ben yehuda
-- strict thread matches above, loose matches on Subject: below --
2009-05-19 16:07 raz ben yehuda
2009-05-19 16:09 raz ben yehuda
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=18963.23693.620765.31533@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=ofer@bitband.com \
--cc=raziebe@gmail.com \
--cc=yaronp@bitband.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).