From: 'Christoph Hellwig' <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
'Mark Haverkamp' <markh@osdl.org>,
linux-scsi@vger.kernel.org
Subject: Re: aacraid driver question
Date: Mon, 25 Aug 2003 20:21:39 +0100 [thread overview]
Message-ID: <20030825202139.A10609@infradead.org> (raw)
In-Reply-To: <0998F43EAD645A47B3F6507196DD70EA2568C6@OTCEXC01>; from mark_salyzyn@adaptec.com on Mon, Aug 25, 2003 at 02:58:01PM -0400
On Mon, Aug 25, 2003 at 02:58:01PM -0400, Salyzyn, Mark wrote:
> It may have been a fools overture for me to do the one driver for all
> kernels, but my build system for providing test and release products is
> currently not geared to multiple sources and this worked for me. So far not
> a problem since we are only releasing to Distribution Kernels ...
Well, if Adaptec doesn't care for mainline we'll better mark
Mark Haverkamp official maintainer. He does a very good job at keeping
the driver uptodate and clean - something that can't be said for
other drivers for adaptec hardware...
> Setting removable true is to force the SCSI subsystem to re-read the
> capacity and partition table on every fresh open since it may have changed
> through an array morph. We used to present the arrays as removable DASD's,
> and recently changed that to present them as Fixed DASD's, to deal with many
> gripes, and setting the removable bit instead when a change occurred.
Well, that's exactly what scsi_rescan_device is for. Mark (H.), could you
try to use it in your 2.6 driver instead?
> A scsi_rescan_device cool, but we have arrays coming, and arrays going. When
> an array goes, I was supposed to mark it offline, the rescan I do right now
> actually hurts under *very* heavy load and takes some time to report the
> deleted array (we managed to stall the report for almost half an hour under
> load, but new devices came online almost instantly). So if I was to make a
> wish list, I would like to make the driver code more robust and also have an
> entry to something like scsi_device_offline (remove single).
That would be scsi_set_device_offline. So what are you doing exactly
in aac_handle_aif? I'll guess now and you correct me, okay?
- AifDenVolumeExtendComplete: a lun has changed size
In 2.6 we'd like to call scsi_rescan_device for this.
- AifDenMorphComplete: some attribute change??
If that's true scsi_rescan_device would be the way to go
aswell.
- AifEnContainerChange: a volume got added or deleted??
If that's the case _and_ we know the channel, id, lun
we can call scsi_add_device / scsi_remove_device
next prev parent reply other threads:[~2003-08-25 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 18:58 aacraid driver question Salyzyn, Mark
2003-08-25 19:21 ` 'Christoph Hellwig' [this message]
2003-08-25 19:27 ` Mark Haverkamp
-- strict thread matches above, loose matches on Subject: below --
2003-08-26 17:05 Salyzyn, Mark
2003-08-26 17:14 ` Mark Haverkamp
2003-08-25 20:50 Salyzyn, Mark
2003-08-26 16:49 ` 'Christoph Hellwig'
2003-08-25 19:56 Salyzyn, Mark
2003-08-25 20:08 ` 'Christoph Hellwig'
2003-08-25 20:25 ` Mark Haverkamp
2003-08-25 20:31 ` 'Christoph Hellwig'
2003-08-26 15:55 ` Mark Haverkamp
2003-08-25 19:32 Salyzyn, Mark
2003-08-25 19:41 ` 'Christoph Hellwig'
[not found] <0998F43EAD645A47B3F6507196DD70EA2568C2@OTCEXC01>
2003-08-25 18:42 ` 'Christoph Hellwig'
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=20030825202139.A10609@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.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