All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
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: Thu, 10 Jul 2008 11:14:43 -0500	[thread overview]
Message-ID: <48763573.7070006@cs.wisc.edu> (raw)
In-Reply-To: <E11DE615-512A-45C0-9308-036BDA225E9D@qlogic.com>

Seokmann Ju wrote:
> Hi,
> 
> With starting to implement FC-CT/ELS support on the qla2xxx module, I 
> would like to get some idea about the bidi-bidirectional.
> As I understand that the bidi is packet transporting infra-structure, I 
> think it could be good candidate for the FC specific FC-CT/ELS packet 
> delivery in between the application and the individual devices given 
> topology.

I think you might also want to look at bsg or really wanted to see bsg 
along with how to support bidi commands? You would want to look at 
block/bsg.c for the bsg driver. And see 
drivers/scsi/scsi_transport_sas.c's sas_bsg_initialize and its 
sas_non_host_smp_request functions for examples of how to send bsg to a 
transport class, and from a class to a class object like a rport 
(replace fc rport for a sas phy though).

  parent reply	other threads:[~2008-07-10 16:14 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
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 [this message]
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=48763573.7070006@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --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 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.