public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Mike Anderson <andmike@us.ibm.com>
Subject: Re: Round II on sysfs attributes
Date: 23 May 2003 15:37:36 -0400	[thread overview]
Message-ID: <1053718657.1810.22.camel@mulgrave> (raw)
In-Reply-To: <20030523113003.A15369@beaverton.ibm.com>

On Fri, 2003-05-23 at 14:30, Patrick Mansfield wrote:
> On Fri, May 23, 2003 at 12:38:24PM -0400, James Bottomley wrote:
> > 
> > The attached patch makes the sysfs attributes a property of the host
> > template (I can't really see a reason why the actual attributes need to
> > change per host, so I think the template is the better place for them).
> > 
> > I've also provided helper functions to modify the attributes in the LLD
> > init routines.
> > 
> > An illustration of how this works for the 53c700 will follow.
> > 
> > James
> 
> Any examples of potential LLDD specific host attributes?

Certainly things like the firmware SEEPROM loading that aic7xxx does. 
Possibly global (or per host) resource counts for HBA's that have single
issue queue (again, aic7xxx; and even the 53c700 has this).

> Looks good for modifying attributes.
> 
> For additional attributes, why not an LLDD specific function to add and
> remove them?

That would require knowledge of what the "official" host attributes are,
so it seemed to me that leaving it up to the routine to determine
whether it's an addition or an override was more appropriate.  If we
have a separate routine for adds it would have to have an error case for
adding an existing resource...

James



  reply	other threads:[~2003-05-23 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 16:38 Round II on sysfs attributes James Bottomley
2003-05-23 18:30 ` Patrick Mansfield
2003-05-23 19:37   ` James Bottomley [this message]
2003-05-23 18:51 ` Mike Anderson
2003-05-23 19:43   ` 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=1053718657.1810.22.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox