From: James Bottomley <James.Bottomley@suse.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Vikas Chaudhary <vikas.chaudhary@qlogic.com>,
linux-scsi@vger.kernel.org, ravi.anand@qlogic.com
Subject: Re: [PATCH 13/15] qla4xxx: Added bsg support
Date: Sat, 12 Jun 2010 17:37:39 -0500 [thread overview]
Message-ID: <1276382259.10508.25.camel@mulgrave.site> (raw)
In-Reply-To: <4C12D398.8020200@cs.wisc.edu>
On Fri, 2010-06-11 at 19:23 -0500, Mike Christie wrote:
> On 06/11/2010 02:49 AM, Vikas Chaudhary wrote:
> > Added BSG support to enable application support to configure
> > ISP40XX/ISP82XX adapter.
> >
> > This patch is on top of: http://marc.info/?l=linux-scsi&m=126999297630764&w=2
> >
>
> Did James say that using vendor specific commands was ok? I did not see
> anything on the list.
In principle, the point about vendor specific host commands has already
been conceded ... lpfc and qla2xxx already use them.
I think the real rule is that for host specific BSG commands, it's only
for stuff that's specific to the host ... so not stuff which should be
done generically.
There are no hard and fast rules for applying the test above. In
theory, the management interfaces exposed by FC_BSG_HST_VENDOR could be
used to send commands ... but it tends to get tolerated as long as the
drivers support the standardised rport commands.
If I look at what the qla4xxx interface would do
1. it only supports vendor specific commands ... this is a bit of a
red flag since it's proposing to do nothing in a vendor neutral
way. This one, I punt back to you: what should an iscsi device
implementing BSG support of the standard commands (which have
only very recently been proposed for definition)
2. QL4_SET_FLASH looks a bit suspicious ... the only thing I think
you could really set from that is the mac addresses ... is this
so?
3. the DDB commands seem to be for manipulating the end point
table ... which is basically the iscsi connection table ... does
manipulating that from BSG make sense?
4. What is ACB and IFCB? It's undocumented
5. GET/SET_ISCSI_STAT seems to be statistics related by the name;
is it? if so, why not use the more standard statistics interface
in the iscsi transport class?
> If he did, then instead of the patch above from
> Jay, you want to use iscsi bsg patches that I sent that handle Tomos's
> comments about not duplicating fc code. I sent the bsg lib to the list
> and then in my tree on kernel.org I ported the fc drivers (those might
> need a update for some patches James Smart recently sent). For those bsg
> patches you will want to then also add the vendor specific command back.
Agreed, having a standard way of doing bsg helps.
James
next prev parent reply other threads:[~2010-06-12 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 7:49 [PATCH 13/15] qla4xxx: Added bsg support Vikas Chaudhary
2010-06-12 0:23 ` Mike Christie
2010-06-12 8:54 ` Vikas Chaudhary
2010-06-12 22:37 ` James Bottomley [this message]
2010-06-13 20:10 ` Mike Christie
2010-06-14 0:55 ` FUJITA Tomonori
2010-06-14 20:48 ` Mike Christie
2010-06-16 2:45 ` Vikas Chaudhary
2010-06-16 2:43 ` Vikas Chaudhary
2010-06-16 11:16 ` Mike Christie
2010-06-16 2:40 ` Vikas Chaudhary
2010-06-16 11:51 ` Mike Christie
2010-06-16 15:42 ` James Bottomley
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=1276382259.10508.25.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=ravi.anand@qlogic.com \
--cc=vikas.chaudhary@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