From: "H . J . Lu" <hjl@lucon.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: hogsberg@users.sourceforge.net, jamesg@filanet.com,
Jens Axboe <axboe@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: sbp2.c on SMP
Date: Sun, 11 Nov 2001 20:54:11 -0800 [thread overview]
Message-ID: <20011111205411.B30782@lucon.org> (raw)
In-Reply-To: <3BEF27D1.7793AE8E@zip.com.au>
In-Reply-To: <3BEF27D1.7793AE8E@zip.com.au>; from akpm@zip.com.au on Sun, Nov 11, 2001 at 05:37:21PM -0800
On Sun, Nov 11, 2001 at 05:37:21PM -0800, Andrew Morton wrote:
>
> With the appended patch I can confirm that the driver happily runs
> `dbench 40' for half an hour on dual x86. Even when you kick the
Thanks a lot.
> disk onto the floor (sorry, HJ).
That is a good stress test.
>
> The games which scsi_old_done() plays with spinlocks and interrupt
> enabling are really foul. If someone calls it with interrupts disabled
> (sbp2 does this) then scsi_old_done() will enable interrupts for you.
> If, for example, you call scsi_old_done() under spin_lock_irqsave(),
> the reenabling of interrupts will expose you to deadlocks. Perhaps
> scsi_old_done() should just use spin_unlock()/spin_lock()?
>
> I tried enabling SBP2_USE_REAL_SPINLOCKS in sbp2.c and that appears to
> work just fine, although I haven't left that change in place here.
>
> You don't actually _need_ SMP hardware to test SMP code, BTW. You
> can just build an SMP kernel and run that on a uniprocessor box.
> This will still catch a wide range of bugs - it certainly detects
> the lockup which was occurring because of the scsi_old_done() thing.
>
> Incidentally, it would be nice to be able to get this driver working
> properly when linked into the kernel - it makes debugging much easier :)
>
I guess I can try that. The only main issue will be the order of
initialization.
H.J.
next prev parent reply other threads:[~2001-11-12 4:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 1:37 sbp2.c on SMP Andrew Morton
2001-11-12 4:54 ` H . J . Lu [this message]
2001-11-12 5:14 ` Andrew Morton
2001-11-12 5:28 ` H . J . Lu
2001-11-12 8:50 ` Alan Cox
2001-11-12 17:34 ` Jens Axboe
2001-11-14 3:17 ` H . J . Lu
2001-11-14 7:21 ` Andrew Morton
2001-11-16 3:32 ` H . J . Lu
2001-11-16 16:15 ` Kristian Hogsberg
2001-11-16 16:30 ` H . J . Lu
2001-11-16 21:25 ` H . J . Lu
2001-11-16 22:40 ` Kristian Hogsberg
2001-11-26 15:43 ` Oops 2.4.15-pre1aa1 Sven Heinicke
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 4:49 sbp2.c on SMP Douglas Gilbert
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=20011111205411.B30782@lucon.org \
--to=hjl@lucon.org \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=hogsberg@users.sourceforge.net \
--cc=jamesg@filanet.com \
--cc=linux-kernel@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.