From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: Will Drewry <wad@chromium.org>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org, snitzer@redhat.com, agk@redhat.com
Subject: Re: [dm-devel] [RFC PATCH v2 1/2] dm: allow a dm-fs-style device to be shared via dm-ioctl
Date: Tue, 18 May 2010 11:36:35 +0900 [thread overview]
Message-ID: <4BF1FD33.4040305@ct.jp.nec.com> (raw)
In-Reply-To: <1273887701-2152-1-git-send-email-wad@chromium.org>
Hi Will,
n 05/15/2010 10:41 AM +0900, Will Drewry wrote:
> In addition, it ensures that public functions are available that
> allow mapped devices and tables to be created and associated
> with the shared code paths with dm-ioctl:
> - suspend flags are available
snip
> diff --git a/drivers/md/dm.h b/drivers/md/dm.h
> index bad1724..782d867 100644
> --- a/drivers/md/dm.h
> +++ b/drivers/md/dm.h
> @@ -17,12 +17,6 @@
> #include <linux/hdreg.h>
>
> /*
> - * Suspend feature flags
> - */
> -#define DM_SUSPEND_LOCKFS_FLAG (1 << 0)
> -#define DM_SUSPEND_NOFLUSH_FLAG (1 << 1)
> -
> -/*
> * Type of table and mapped_device's mempool
> */
> #define DM_TYPE_NONE 0
> diff --git a/include/linux/device-mapper.h b/include/linux/device-mapper.h
> index 1381cd9..6c1c230 100644
> --- a/include/linux/device-mapper.h
> +++ b/include/linux/device-mapper.h
> @@ -215,6 +215,18 @@ void dm_set_mdptr(struct mapped_device *md, void *ptr);
> void *dm_get_mdptr(struct mapped_device *md);
>
> /*
> + * Export the device via the ioctl interface (uses mdptr).
> + */
> +int dm_ioctl_export(struct mapped_device *md, const char *name,
> + const char *uuid);
> +
> +/*
> + * Suspend feature flags
> + */
> +#define DM_SUSPEND_LOCKFS_FLAG (1 << 0)
> +#define DM_SUSPEND_NOFLUSH_FLAG (1 << 1)
> +
> +/*
> * A device can still be used while suspended, but I/O is deferred.
> */
> int dm_suspend(struct mapped_device *md, unsigned suspend_flags);
Why do you need suspend feature flags?
I think no feature is needed (specifying '0' is enough) to make/suspend
a dm device at boot time (although I have looked at only this flag part).
Am I missing something?
Thanks,
Kiyoshi Ueda
next prev parent reply other threads:[~2010-05-18 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100514035347.GA20636@redhat.com>
2010-05-15 1:41 ` [RFC PATCH v2 1/2] dm: allow a dm-fs-style device to be shared via dm-ioctl Will Drewry
2010-05-18 2:36 ` Kiyoshi Ueda [this message]
2010-05-18 3:11 ` [dm-devel] " Will Drewry
2010-05-15 1:41 ` [RFC PATCH v2 2/2] init: boot to device-mapper targets without an initr* Will Drewry
2010-05-17 16:47 ` Randy Dunlap
2010-05-17 18:13 ` Will Drewry
2010-05-17 18:21 ` Randy Dunlap
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=4BF1FD33.4040305@ct.jp.nec.com \
--to=k-ueda@ct.jp.nec.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=wad@chromium.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