From: Mike Anderson <andmike@us.ibm.com>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: linux-raid@vger.kernel.org,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH]: HotSwap SCSI in Soft RAID1 (scsi_rescan)
Date: Fri, 20 Sep 2002 12:35:47 -0700 [thread overview]
Message-ID: <20020920193547.GA3237@beaverton.ibm.com> (raw)
In-Reply-To: <A5974D8E5F98D511BB910002A50A66470580D1EC@hdsmsx103.hd.intel.com>
Cress, Andrew R [andrew.r.cress@intel.com] wrote:
> --- linux-2.4.18-orig/drivers/scsi/scsi.c Wed Aug 28 20:38:13 2002
> +++ linux-2.4.18/drivers/scsi/scsi.c Thu Aug 29 08:08:57 2002
> @@ -1999,6 +1999,9 @@
> (*sdtpnt->finish) ();
> }
> }
> + for (shpnt = scsi_hostlist; shpnt; shpnt = shpnt->next) {
> + shpnt->init_done = 1;
> + }
> }
This could probably be done in a upper loop (maybe not to avoid unit
attentions) or at least only on the adapter template that is being
registered.
> +
> + if (!in_interrupt()) {
> + /* Check if we need to rescan after a reset.
> ARC*/
> + if (SDpnt->host->need_scan == 1) {
> + SDpnt->host->need_scan = 2;
> + spin_unlock_irq(&io_request_lock);
> + scsi_rescan(SDpnt->host,SDpnt->channel);
> + spin_lock_irq(&io_request_lock);
> + SDpnt->host->need_scan = 0;
> + }
> + }
> }
I do not have a suggestion on where to move this, but you could be
called under memory pressure which is probably not the best
time to be allocating chunks of memory.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2002-09-20 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 17:17 [PATCH]: HotSwap SCSI in Soft RAID1 (scsi_rescan) Cress, Andrew R
2002-09-20 18:51 ` Patrick Mansfield
2002-09-20 19:35 ` Mike Anderson [this message]
2002-09-20 23:56 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 21:12 Cress, Andrew R
2002-09-23 14:40 Cress, Andrew R
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=20020920193547.GA3237@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=andrew.r.cress@intel.com \
--cc=linux-raid@vger.kernel.org \
--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