From: David Hinds <dhinds@sonic.net>
To: David Gibson <hermes@gibson.dropbear.id.au>,
Ian Morgan <imorgan@webcon.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: in-kernel pcmcia oopsing in SMP
Date: Sun, 16 Dec 2001 20:59:50 -0800 [thread overview]
Message-ID: <20011216205950.B21159@sonic.net> (raw)
In-Reply-To: <20011201120541.B28295@sonic.net> <Pine.LNX.4.40.0112011513041.2329-100000@light.webcon.net> <20011201124630.A30249@sonic.net> <20011217142400.L30975@zax>
In-Reply-To: <20011217142400.L30975@zax>
On Mon, Dec 17, 2001 at 02:24:00PM +1100, David Gibson wrote:
>
> > Your oops, in tasklet code, sounds to me like a locking bug in the
> > driver code for managing the transmit stack vs. interrupt handling.
> > Have there been reports of the driver working well on SMP boxes?
>
> Well, one of the main features of the driver is that the Tx path and
> the interupt handler (Rx path) are permitted to run concurrently.
> This is an issue even on UP (although not as complex), since the Rx
> patch can interrupt the Tx path. I believe there has been at least
> some successful operation on SMP machines, but unfortunately I don't
> know any details.
Yes, after I wrote that, I looked at the orinoco code, and the tx and
interrupt paths looked pretty straightforward. But I don't think I
would be able to catch anything that wasn't really obvious.
-- Dave
next prev parent reply other threads:[~2001-12-17 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 19:21 in-kernel pcmcia oopsing in SMP Ian Morgan
2001-12-01 20:05 ` David Hinds
2001-12-01 20:27 ` Ian Morgan
2001-12-01 20:46 ` David Hinds
2001-12-17 3:24 ` David Gibson
2001-12-17 4:59 ` David Hinds [this message]
2001-12-03 3:25 ` BUG() in spinlock.h loading ds.o Ian Morgan
2001-12-03 6:56 ` David Hinds
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=20011216205950.B21159@sonic.net \
--to=dhinds@sonic.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=imorgan@webcon.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox