All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Studenmund <wrstuden@apple.com>
To: open-iscsi@googlegroups.com
Cc: dougg@torque.net, Boaz Harrosh <bharrosh@panasas.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	Mike Christie <michaelc@cs.wisc.edu>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel.E.Messinger@seagate.com, Liran Schour <LIRANS@il.ibm.com>
Subject: Re: [RFC 1/6] bidi support: request dma_data_direction
Date: Mon, 22 Jan 2007 13:53:27 -0800	[thread overview]
Message-ID: <A5D5F816-B98C-4637-B92F-E2AAF37469D3@apple.com> (raw)
In-Reply-To: <45B4547A.3020105@panasas.com>

On Jan 21, 2007, at 10:06 PM, Benny Halevy wrote:

> Douglas Gilbert wrote:
>> Boaz Harrosh wrote:
>>> - Introduce a new enum dma_data_direction data_dir member in  
>>> struct request.
>>>   and remove the RW bit from request->cmd_flag
>>> - Add new API to query request direction.
>>> - Adjust existing API and implementation.
>>> - Cleanup wrong use of DMA_BIDIRECTIONAL
>>> - Introduce new blk_rq_init_unqueued_req() and use it in places  
>>> ad-hoc
>>>   requests were used and bzero'ed.
>>
>> With a bi-directional transfer is it always unambiguous
>> which transfer occurs first (or could they occur at
>> the same time)?
>
> The bidi transfers can occur in any order and in parallel.

Yes.

However it's not that hard. If you're a target (which open-iscsi  
isn't), you know what the command needs. If you're an initiator, you  
just send the unsolicited data (if any), then let the target tell you  
what it needs next.

While it is possible for commands to have multiple phases, all the  
BiDi commands I'm familiar with use the Data-Out phase to send extra  
command data, then use the Data-In phase to get either an extended  
response to the query (such as a search command) or extended status  
(OSD commands). So it's not that bad in reality.

Take care,

Bill

  parent reply	other threads:[~2007-01-22 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 23:21 [RFC 1/6] bidi support: request dma_data_direction Boaz Harrosh
2007-01-22  0:24 ` Douglas Gilbert
2007-01-22  6:06   ` Benny Halevy
2007-01-22 15:05     ` Douglas Gilbert
2007-01-22 15:31       ` James Bottomley
2007-01-23 13:37       ` Benny Halevy
2007-01-22 21:53     ` William Studenmund [this message]
2007-01-22  5:29 ` Muli Ben-Yehuda
2007-01-23 13:45   ` Benny Halevy
2007-01-23 14:37     ` Muli Ben-Yehuda
2007-01-23 15:17       ` Benny Halevy

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=A5D5F816-B98C-4637-B92F-E2AAF37469D3@apple.com \
    --to=wrstuden@apple.com \
    --cc=Daniel.E.Messinger@seagate.com \
    --cc=LIRANS@il.ibm.com \
    --cc=bharrosh@panasas.com \
    --cc=dougg@torque.net \
    --cc=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=open-iscsi@googlegroups.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.