All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: "Singh, Santosh (STSD)" <santosh.singh3@hp.com>
Cc: "P S, Suresh (STSD)" <suresh.pathamadai@hp.com>, dm-devel@redhat.com
Subject: Re: Next set of device-mapper  patches
Date: Wed, 21 Jun 2006 13:44:15 +0200	[thread overview]
Message-ID: <4499310F.3000007@redhat.com> (raw)
In-Reply-To: <3EC60E80D9AA7C4E910ACC9DA2003AC30606C55C@BGEEXC02.asiapacific.cpqcorp.net>

Hello,

ioctl patch simple route ioctls to underlying block device
-> it supports all ioctl which are supported by your physical device.

e.g.
in simple case you have volume /dev/mapper/VolGroup00-LogVol0
mapped to physical device /dev/sda, inquiry ioctl (using tools from sg3_util)
sg_inq /dev/sda   
	is the same as
sg_inq /dev/mapper/VolGroup00-LogVol0

In the case of multipath target ioctl command is sent through
active path.

This patch doesn't add some special ioctls to manage dm devices yet.

Milan

--
Milan Broz
mbroz@redhat.com

Singh, Santosh (STSD) wrote:
>  Hi Broz,
> 
> I build  the device-mapper ioctl patches created  by you & Alasdair. I
> am able to load the modules but wanted to know how to  use the ioctl
> call or how to issue the  ioctl call on the device mapper devices.
> 
> 
> Thanks & Regards
> Santosh Singh
> Hewlett-Packard
> 
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Alasdair G Kergon
> Sent: Thursday, June 15, 2006 9:47 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Next set of device-mapper patches
> 
> On Thu, Jun 15, 2006 at 09:16:56PM +0530, Singh, Santosh (STSD) wrote:
>> I tried to patch on 2.6.16 as following and got the error below
>  
> Strange.  That file got truncated.  I've uploaded it again.
> 
> Alasdair
> --
> agk@redhat.com
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 

       reply	other threads:[~2006-06-21 11:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3EC60E80D9AA7C4E910ACC9DA2003AC30606C55C@BGEEXC02.asiapacific.cpqcorp.net>
2006-06-21 11:44 ` Milan Broz [this message]
2006-06-21 13:07   ` Next set of device-mapper patches AJ Lewis
2006-06-21 13:26     ` Milan Broz
2006-07-03 16:29       ` Singh, Santosh (STSD)
     [not found] <20060610160024.36F82733FA@hormel.redhat.com>
2006-06-15 14:52 ` Singh, Santosh (STSD)
2006-06-15 14:56   ` Next " Alasdair G Kergon
2006-06-15 15:12     ` Singh, Santosh (STSD)
2006-06-15 15:20       ` Alasdair G Kergon
2006-06-15 15:46         ` Singh, Santosh (STSD)
2006-06-15 16:16           ` Alasdair G Kergon
2006-06-16 14:31             ` Singh, Santosh (STSD)
2006-06-16 14:36             ` Singh, Santosh (STSD)
2006-06-09 21:22 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=4499310F.3000007@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=santosh.singh3@hp.com \
    --cc=suresh.pathamadai@hp.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.