From: James Smart <James.Smart@Emulex.Com>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi : set target can_queue from devinfo flags
Date: Wed, 14 May 2008 10:39:44 -0400 [thread overview]
Message-ID: <482AF9B0.7090307@emulex.com> (raw)
In-Reply-To: <482A87EF.4010002@suse.de>
Hannes Reinecke wrote:
>> This patch was cut against scsi-misc-2.6, and depends on Mike
>> Christies patches
>> contained in the original thread.
>>
> Hmph.
>
> I don't quite agree with this one.
> For once, /proc/scsi/scsi has been marked as 'obsolete' for quite some
> time now,
> so adding other usages to this is of questionable value.
Um... I didn't think I added a new use for it. The existing data had to
be extended by an additional argument.
>
> And we've actually have a similar issue when developing the SCSI
> device_handler
> stuff where we also have a device list to maintain.
>
> Seeing there is quite some overlap between those two cases I think we
> should
> come up with a way of handling these things properly, ie tied into sysfs.
Ok - but I see it as a two part process. I am not signing up for replacing
the device list infrastructure. But, now that there is target queue depth
management in the midlayer, I believe we should be taking advantage of it.
I'd rather see the additional field go in, then see a separate effort to
replace/collapse the device lists...
> So, what we should do here is
> a) add a 'can_queue' sysfs attribute to the starget (which we can
> nowadays, as
> the starget is a proper sysfs object)
Um, it exists under the /sys/devices tree (the base object) but there is no
class representation. Are you requesting this goes on the base object ?
I thought we avoided this. I guess it can, but as it's scsi-ish, I would
think it more appropriate to formally create a scsi_target class and put
scsi attributes there. (but I was avoiding that too)
> b) define a 'modalias' style definition for matching SCSI vendor/model/rev
> and create a scsi_devinfo module from which all these special cases
> can be invoked from.
>
> That would also allow us to get rid of the device tables in the
> device_handler
> modules which I never really liked.
>
> What do you think?
see above.
-- james s
>
> Cheers,
>
> Hannes
next prev parent reply other threads:[~2008-05-14 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 17:45 [PATCH] scsi : set target can_queue from devinfo flags James Smart
2008-05-14 6:34 ` Hannes Reinecke
2008-05-14 14:39 ` James Smart [this message]
2008-05-14 15:01 ` Hannes Reinecke
2008-05-14 19:38 ` James Bottomley
2008-05-14 21:50 ` James Smart
2008-05-15 1:21 ` James Smart
2008-09-24 19:13 ` Mike Christie
2008-09-24 19:17 ` Mike Christie
2008-09-25 18:40 ` Mike Christie
2008-09-25 19:03 ` James Smart
2008-09-24 19:38 ` James Smart
2008-09-25 18:15 ` Mike Christie
2008-09-26 7:46 ` Hannes Reinecke
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=482AF9B0.7090307@emulex.com \
--to=james.smart@emulex.com \
--cc=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox