All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: bugs in handling of errors for SG_IO and SCSI_IOCT L_SEND_COMMAND ioctls to block device
Date: Fri, 08 Jul 2005 11:48:08 -0500	[thread overview]
Message-ID: <42CEAE48.9050203@cs.wisc.edu> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321AB53@SRMANNING.eng.emc.com>

goggin, edward wrote:
> On Thu, 07 Jul 2005 23:19:57 -0500
> Mike Christie <michaelc@cs.wisc.edu> wrote
> 
> 
>>>...
>>>
>>>	The bio handling for these REQ_BLOCK_PC requests shouldn't be
>>>treated any
>>>	differently than the more typical REQ_CMD type block io request.
>>
> 
>>what is meant by this last comment specifically?
> 
> 
> Just trying to make a case that a device pass through read command
> issued to a block device should transfer to user space only the
> user requested number of bytes minus the residual from the transfer
> (as is done for block device read and write requests) and not always
> transfer the number of bytes requested by the user.
> 

ah ok, I thought it was referring to something else, nevermind.

Was the reason it does SG_IO reads becuase opens on the device were not 
allowed? Was not being able to open a dm device a bug or by design? For 
devices that do not support SG_IO like NBD, dasd and if you do 
dm-multipath with AOE, another solution may have to be found.

  reply	other threads:[~2005-07-08 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 16:32 bugs in handling of errors for SG_IO and SCSI_IOCT L_SEND_COMMAND ioctls to block device goggin, edward
2005-07-08 16:48 ` Mike Christie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-09 22:58 goggin, edward

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=42CEAE48.9050203@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=dm-devel@redhat.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.