All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Sven Schuetz <sven@linux.vnet.ibm.com>
Cc: Seokmann Ju <seokmann.ju@qlogic.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Robert W Love <robert.w.love@intel.com>
Subject: Re: [PATCH 0/2] FC pass through support via bsg interface
Date: Mon, 3 Nov 2008 11:00:19 -0500	[thread overview]
Message-ID: <490F2013.70507@emulex.com> (raw)
In-Reply-To: <490EEB18.2060402@linux.vnet.ibm.com>



Sven Schuetz wrote:
> Hi Seokmann,
> 
> first of all, thanks for your efforts so far, good work!

I second this!

> Regarding the following statement from James and your question to it:
> 
> Seokmann Ju wrote:
>> On Sep 12, 2008, at 9:49 AM, James Smart wrote:
>>
>>> Seokmann,
>>>
>>> There are number of fundamental issues with this patch that need to be
>>> corrected. I'll be at plumbers conference next week, and will be able
>>> to work through this. Please look me up if you will be there.
>>> Otherwise, I'll just post a revised patch.
>>>
>>> Here are the issues as I see them:
>>>
> 
> <snip>
> 
>>> - We really should add support, for the initial merge, to talk to an
>>>  address that doesn't exist via an rport (think fabric service).
>>>  This means adding some request types to the fc_host too.
>> This one too, please.
>>> -- james s
>>>
> 
> <snip>
> 
> 
>  From what I have seen, that's still missing from your latest submission. What
> James means by that (James, correct me when I am wrong) is that at the moment we
> only have devices for rports under /dev.
> That's good for ELS requests, but for CT requests that are not directed to
> individual rports but to some well known address that's not appropriate. I think
> there might also be situations when there are no rports available and yet you
> still want to issue a CT request. In my opinion we would need devices for the
> fc_hosts under /dev as well. I have not looked at it in detail yet but it
> probably means to add a device struct to the fc_host_attrs struct similar as it
> is done for rports and register them with the block layer as well. Maybe it's
> feasible to have a dedicated ELS and CT handler in the transport layer instead
> of a generic service handler than (CT requets come in via /dev/fc_hostx and are
> handled by some fc_ct_service function and ELS requests come in via
> /dev/rportxxx and are handled by sme fc_els_service function), but that's
> something that needs to be looked at.
> If you already have some ideas on how to do that, please let me know. I might
> start some experiments as well if I find the time.
> 
> Sven

I've started this work, and am merging it with Seokman's patches.  The 
recent respins have reset it.  This work is also good for validating the 
  request/response formats, as it extends the requests to target 
transport handlers that do more than ELS/CT. So it's a good reference to 
ensure things are partitioned correctly.

Seokman:  I applied your last "revised III" patches - and the qla (2nd) 
patch failed miserably against scsi-misc-2.6. What were the patches cut 
against ?

-- james s


  reply	other threads:[~2008-11-03 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 14:03 [PATCH 0/2] FC pass through support via bsg interface Seokmann Ju
2008-09-12 16:49 ` James Smart
2008-09-15 16:21   ` Seokmann Ju
2008-11-03 12:14     ` Sven Schuetz
2008-11-03 16:00       ` James Smart [this message]
2008-11-03 16:39         ` Seokmann Ju
2008-11-18 14:17         ` Sven Schuetz
2008-11-03 16:33       ` Seokmann Ju
2008-09-15 20:06   ` FUJITA Tomonori
2008-09-16  1:00     ` 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=490F2013.70507@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=robert.w.love@intel.com \
    --cc=seokmann.ju@qlogic.com \
    --cc=sven@linux.vnet.ibm.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.