From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: olson@unixfolk.com, mingo@elte.hu, ccb@acm.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
Date: Tue, 20 Jun 2006 01:03:55 -0700 [thread overview]
Message-ID: <20060620010355.a4d1348a.akpm@osdl.org> (raw)
In-Reply-To: <4497A5BC.4070005@yahoo.com.au>
On Tue, 20 Jun 2006 17:37:32 +1000
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >>Kernel panic - not syncing: nmi watchdog
>
> Any ideas what it might be waiting on?
Readers, I guess. When there's a spinning writer, nothing prevents _new_
readers from getting into the read-locked region. If we have enough
readers and the read-locked region is long enough, there's always at least
one reader in the read-locked region and the writer is permanently starved.
> Otherwise, a straight rwlock->spinlock conversion will have a few more
> scalability issues, but I'd guess it wouldn't be a problem at all for
> most workloads on most systems.
It beats crashing.
next prev parent reply other threads:[~2006-06-20 8:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.VT2rwoX1M/2O/aO5crhlRDNx4YA@ifi.uio.no>
[not found] ` <fa.Zp589GPrIISmAAheRowfRgZ1jgs@ifi.uio.no>
2006-06-20 5:35 ` Dave Olson
2006-06-20 6:39 ` Andrew Morton
2006-06-20 6:53 ` Dave Jones
2006-06-20 7:37 ` Nick Piggin
2006-06-20 8:03 ` Andrew Morton [this message]
2006-06-20 8:33 ` Ingo Molnar
2006-06-20 9:37 ` Nick Piggin
2006-06-20 9:51 ` Ingo Molnar
2006-06-20 10:59 ` Nick Piggin
2006-06-20 13:04 ` Arjan van de Ven
2006-06-20 13:28 ` update pci device id cckuo
2006-06-20 14:06 ` Arjan van de Ven
2006-06-20 13:36 ` [patch] increase spinlock-debug looping timeouts (write_lock and NMI) Nick Piggin
2006-06-20 14:53 ` Arjan van de Ven
2006-06-20 15:16 ` Nick Piggin
2006-06-20 16:27 ` Nick Piggin
2006-06-20 8:43 ` Arjan van de Ven
2006-06-20 16:11 ` Dave Olson
2006-06-20 21:10 ` Andrew Morton
2006-06-22 5:45 Dave Olson
2006-06-22 5:57 ` Andrew Morton
2006-06-23 7:57 ` Ingo Molnar
2006-06-23 16:27 Dave Olson
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=20060620010355.a4d1348a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ccb@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=olson@unixfolk.com \
/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
all inboxes | Powered by JetHome®