From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Chris Leech <chris.leech@gmail.com>
Cc: James Smart <James.Smart@emulex.com>,
Seokmann Ju <seokmann.ju@qlogic.com>,
Robert W Love <robert.w.love@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Boaz Harrosh <bharrosh@panasas.com>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [RFC] pass through support in fc transport: via bsg (block SG)
Date: Fri, 22 Aug 2008 15:48:46 -0700 [thread overview]
Message-ID: <20080822224846.GH9169@plap4-2.local> (raw)
In-Reply-To: <41b516cb0808221535n1d009bdaxb6ae6136b1f68c18@mail.gmail.com>
On Fri, 22 Aug 2008, Chris Leech wrote:
> > That's essentially what prompted this inquiry. Sure, for hardware
> > CNA/HBA solutions, access to something like a raw-frame header seems
> > unnecessary. What about software FCoE? Would the openfcoe want this
> > export/expose these raw-frame data?
>
> It's easy enough to provide software assists for lower level devices,
> so I'd say focus on what will work for HBAs and we'll make software
> FCoE work around that interface. I don't see a reason to expose any
> extra level of detail here, if you want to see the full frame data in
> the software FCoE case you can always just capture the network
> traffic.
Fair enough...
next prev parent reply other threads:[~2008-08-22 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 19:04 [RFC] pass through support in fc transport: via bsg (block SG) Seokmann Ju
2008-08-19 17:42 ` Seokmann Ju
2008-08-22 21:36 ` Seokmann Ju
2008-08-22 21:53 ` James Smart
2008-08-22 22:09 ` Andrew Vasquez
2008-08-22 22:35 ` Chris Leech
2008-08-22 22:48 ` Andrew Vasquez [this message]
2008-08-23 14:43 ` James Smart
2008-09-11 13:25 ` Seokmann Ju
2008-09-11 13:44 ` James Smart
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=20080822224846.GH9169@plap4-2.local \
--to=andrew.vasquez@qlogic.com \
--cc=James.Smart@emulex.com \
--cc=bharrosh@panasas.com \
--cc=chris.leech@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=robert.w.love@intel.com \
--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