From: Shaohua Li <shli@kernel.org>
To: heinzm@redhat.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/2] md: add raid4/5/6 journal mode API (for dm-raid use)
Date: Fri, 24 Mar 2017 10:29:15 -0700 [thread overview]
Message-ID: <20170324172915.ke2zktnft64dtr6n@kernel.org> (raw)
In-Reply-To: <20170322164423.20972-2-heinzm@redhat.com>
On Wed, Mar 22, 2017 at 05:44:22PM +0100, heinzm@redhat.com wrote:
> From: Heinz Mauelshagen <heinzm@redhat.com>
>
> Upstream commit 2ded370373a400c20cf0c6e941e724e61582a867
> started the addition of "write-back" mode to MD (raid5-cache),
> i.e. support write-back caching on the raid journal device.
>
> In order to allow the dm-raid target to switch between
> the available "write-through" and "write-back" modes,
> provide new r5c_journal_mode_set() API.
>
> Use the new API in existing r5c_journal_mode_store()
Looks good to me, if this will be routed through dm tree, you can add:
Acked-by: Shaohua Li <shli@fb.com>
> Signed-off-by: Heinz Mauelshagen <heinzm@redhat.com>
> ---
> drivers/md/raid5-cache.c | 62 ++++++++++++++++++++++++++----------------------
> drivers/md/raid5.h | 11 +++++++++
> 2 files changed, 45 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
> index 3f307be..218b6f3 100644
> --- a/drivers/md/raid5-cache.c
> +++ b/drivers/md/raid5-cache.c
> @@ -53,16 +53,6 @@
> */
> #define R5L_POOL_SIZE 4
>
> -/*
> - * r5c journal modes of the array: write-back or write-through.
> - * write-through mode has identical behavior as existing log only
> - * implementation.
> - */
> -enum r5c_journal_mode {
> - R5C_JOURNAL_MODE_WRITE_THROUGH = 0,
> - R5C_JOURNAL_MODE_WRITE_BACK = 1,
> -};
> -
> static char *r5c_journal_mode_str[] = {"write-through",
> "write-back"};
> /*
> @@ -2327,40 +2317,56 @@ static ssize_t r5c_journal_mode_show(struct mddev *mddev, char *page)
> return ret;
> }
>
> -static ssize_t r5c_journal_mode_store(struct mddev *mddev,
> - const char *page, size_t length)
> +/*
> + * Set journal cache mode on @mddev (external API initially needed by dm-raid).
> + *
> + * @mode as defined in 'enum r5c_journal_mode'.
> + *
> + */
> +int r5c_journal_mode_set(struct mddev *mddev, int mode)
> {
> struct r5conf *conf = mddev->private;
> struct r5l_log *log = conf->log;
> - int val = -1, i;
> - int len = length;
>
> if (!log)
> return -ENODEV;
>
> - if (len && page[len - 1] == '\n')
> - len -= 1;
> - for (i = 0; i < ARRAY_SIZE(r5c_journal_mode_str); i++)
> - if (strlen(r5c_journal_mode_str[i]) == len &&
> - strncmp(page, r5c_journal_mode_str[i], len) == 0) {
> - val = i;
> - break;
> - }
> - if (val < R5C_JOURNAL_MODE_WRITE_THROUGH ||
> - val > R5C_JOURNAL_MODE_WRITE_BACK)
> + if (mode < R5C_JOURNAL_MODE_WRITE_THROUGH ||
> + mode > R5C_JOURNAL_MODE_WRITE_BACK)
> return -EINVAL;
>
> if (raid5_calc_degraded(conf) > 0 &&
> - val == R5C_JOURNAL_MODE_WRITE_BACK)
> + mode == R5C_JOURNAL_MODE_WRITE_BACK)
> return -EINVAL;
>
> mddev_suspend(mddev);
> - conf->log->r5c_journal_mode = val;
> + conf->log->r5c_journal_mode = mode;
> mddev_resume(mddev);
>
> pr_debug("md/raid:%s: setting r5c cache mode to %d: %s\n",
> - mdname(mddev), val, r5c_journal_mode_str[val]);
> - return length;
> + mdname(mddev), mode, r5c_journal_mode_str[mode]);
> + return 0;
> +}
> +EXPORT_SYMBOL(r5c_journal_mode_set);
> +
> +static ssize_t r5c_journal_mode_store(struct mddev *mddev,
> + const char *page, size_t length)
> +{
> + int mode = ARRAY_SIZE(r5c_journal_mode_str);
> + size_t len = length;
> +
> + if (len < 2)
> + return -EINVAL;
> +
> + if (page[len - 1] == '\n')
> + len--;
> +
> + while (mode--)
> + if (strlen(r5c_journal_mode_str[mode]) == len &&
> + !strncmp(page, r5c_journal_mode_str[mode], len))
> + break;
> +
> + return r5c_journal_mode_set(mddev, mode) ?: length;
> }
>
> struct md_sysfs_entry
> diff --git a/drivers/md/raid5.h b/drivers/md/raid5.h
> index 4bb27b9..ec8ca15 100644
> --- a/drivers/md/raid5.h
> +++ b/drivers/md/raid5.h
> @@ -547,6 +547,16 @@ struct r5worker_group {
> int stripes_cnt;
> };
>
> +/*
> + * r5c journal modes of the array: write-back or write-through.
> + * write-through mode has identical behavior as existing log only
> + * implementation.
> + */
> +enum r5c_journal_mode {
> + R5C_JOURNAL_MODE_WRITE_THROUGH = 0,
> + R5C_JOURNAL_MODE_WRITE_BACK = 1,
> +};
> +
> enum r5_cache_state {
> R5_INACTIVE_BLOCKED, /* release of inactive stripes blocked,
> * waiting for 25% to be free
> @@ -795,4 +805,5 @@ extern void r5c_check_cached_full_stripe(struct r5conf *conf);
> extern struct md_sysfs_entry r5c_journal_mode;
> extern void r5c_update_on_rdev_error(struct mddev *mddev);
> extern bool r5c_big_stripe_cached(struct r5conf *conf, sector_t sect);
> +extern int r5c_journal_mode_set(struct mddev *mddev, int journal_mode);
> #endif
> --
> 2.9.3
>
> --
> 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
prev parent reply other threads:[~2017-03-24 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 16:44 [PATCH 1/2] md: add raid4/5/6 journal mode API (for dm-raid use) heinzm
2017-03-24 17:29 ` Shaohua Li [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=20170324172915.ke2zktnft64dtr6n@kernel.org \
--to=shli@kernel.org \
--cc=heinzm@redhat.com \
--cc=linux-raid@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 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).