From: "Sandeep K Sinha" <sandeepksinha@gmail.com>
To: "Sandeep K Sinha" <sandeepksinha@gmail.com>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: Device mapper support for more than one target ?
Date: Tue, 23 Dec 2008 00:24:49 +0530 [thread overview]
Message-ID: <37d33d830812221054w78fe49f3l6c2896a27c908656@mail.gmail.com> (raw)
In-Reply-To: <20081222185033.GA17119@agk.fab.redhat.com>
Hey,
On Tue, Dec 23, 2008 at 12:20 AM, Alasdair G Kergon <agk@redhat.com> wrote:
> On Mon, Dec 22, 2008 at 10:52:08PM +0530, Sandeep K Sinha wrote:
>> After looking at the complete implementation of device mappers, I
>> figured out that we can have more than one target for a mapped device
>> then why do we have a check for the number of target to be equal to
>> one , in dm_blk_ioctl ( ) in drivers/md/dm.c
>>
>> http://lxr.linux.no/linux+v2.6.27.10/drivers/md/dm.c#L337
>
> Because whether or not it makes sense to send any specific ioctl to more
> than one target in parallel depends on what that ioctl does. When we
> added that code we said that we could add hard-coding for specific
> ioctls if the need arose, but so far it hasn't.
>
No, the philosophy should be that we send the ioctl's to the mapped
device and not to the targets underlying that mapped-device.
And doing so, I should be able to access the complete map that belongs
to that mapped device. If I implement an ioctl of my own and try to
serve it, the problem would be that it would never allow me to serve
it if has more than one target.
> Alasdair
> --
> agk@redhat.com
>
--
Regards,
Sandeep.
"To learn is to change. Education is a process that changes the learner."
next prev parent reply other threads:[~2008-12-22 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 17:22 Sandeep K Sinha
2008-12-22 18:50 ` Alasdair G Kergon
2008-12-22 18:54 ` Sandeep K Sinha [this message]
2008-12-22 19:03 ` Sandeep K Sinha
2008-12-22 21:24 ` [dm-devel] " Alasdair G Kergon
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=37d33d830812221054w78fe49f3l6c2896a27c908656@mail.gmail.com \
--to=sandeepksinha@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®