From: Boaz Harrosh <bharrosh@panasas.com>
To: Seokmann Ju <seokmann.ju@qlogic.com>
Cc: linux-scsi@vger.kernel.org, Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: bidi support: FC transport layer...
Date: Sun, 13 Jul 2008 12:15:32 +0300 [thread overview]
Message-ID: <4879C7B4.8000609@panasas.com> (raw)
In-Reply-To: <4414E10D-6015-4768-BD97-D4A51E439573@qlogic.com>
Seokmann Ju wrote:
<snip>
> FC-CT and ELS are FC specifics.
> So, as far as I understood, the idea is to control and manage the
> given FC layout via those frames without having any subsystem
> interventions.
> One of the goal of the implementation is to provide pipe line in
> between the application and the target devices under the given layout.
> Is the bidi tightly coupled with the SCSI CDB, or it can transport any
> packet regardless its contents?
>
There is *no* restrictions or filtering what so ever. You can send any
kind of CDB with any kind of buffers as BIOs. Even better, the scsi
midlayer is very careful to immediately fail a bidi command and not
try any kind of reties or error handling. So yes if you are emulating
a command execution in SW you should be safe. What I said is true at
scsi level, at block level of course there is no restrictions for
any command.
<snip>
Boaz
next prev parent reply other threads:[~2008-07-13 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 12:55 bidi support: FC transport layer Seokmann Ju
2008-07-10 15:30 ` Boaz Harrosh
2008-07-10 16:36 ` Seokmann Ju
2008-07-13 9:15 ` Boaz Harrosh [this message]
2008-07-10 16:10 ` James.Smart
2008-07-10 20:28 ` Seokmann Ju
2008-07-15 18:54 ` Seokmann Ju
2008-07-15 19:35 ` James.Smart
2008-07-16 17:53 ` Seokmann Ju
2008-07-17 13:57 ` Seokmann Ju
2008-07-17 17:25 ` James.Smart
2008-07-10 16:14 ` Mike Christie
2008-07-10 18:13 ` Seokmann Ju
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=4879C7B4.8000609@panasas.com \
--to=bharrosh@panasas.com \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=seokmann.ju@qlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox