All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: James Smart <James.Smart@Emulex.Com>
Cc: "James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	Krishna Gudipati <gudipati@usc.edu>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Creating a subdirectory under fc_host statistics using fc_function_template
Date: Sun, 04 Jan 2009 11:17:41 -0600	[thread overview]
Message-ID: <4960EF35.2090502@cs.wisc.edu> (raw)
In-Reply-To: <494A86DE.7020908@emulex.com>

James Smart wrote:
> James,
> 
> What Krishna describes, is a need to add driver-specific attributes (and 
> optionally a directory of attributes) to a class-level object. I 
> attempted patches of a similar form when I was originally doing the 
> fc_rports, which were rejected.
> 
> I believe the position is that we do not allow driver-specific things on 
> the class objects, and drivers are limited in scope to only adding 
> individual attributes to the scsi_host via the attribute list in the 
> scsi_host_template.
> 
> I'd like to re-propose the patches to add driver-specific data to the FC 
> class objects. Do you believe there's a change in heart to accepting 
> this functionality before I start the work to create them ?
> 
> For example, I know that Emulex would have liked to add driver-specific 
> state data to the rports.  And Krishna's proposal is another request.
> 

We are having the same problem for iscsi. For qla4xxx and cxgb3i and 
bnx2i, we would like to add driver specific attrs to the iscsi 
session/connection which are like FC's rport struct.

I was hoping if at least the classes provide an API to add driver 
specific attrs similar to how scsi-ml does, then it would be ok?

  reply	other threads:[~2009-01-04 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 19:39 Creating a subdirectory under fc_host statistics using fc_function_template Krishna Gudipati
2008-12-18 17:22 ` James Smart
2009-01-04 17:17   ` Mike Christie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-10 19:20 Krishna Gudipati

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=4960EF35.2090502@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Smart@Emulex.Com \
    --cc=gudipati@usc.edu \
    --cc=linux-scsi@vger.kernel.org \
    /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.