Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)

On Tue, 20 Jun 2006 17:37:32 +1000
Nick Piggin <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Dave Olson <[email protected]>
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Andrew Morton <[email protected]>
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
• Next by Date: Re: emergency or init=/bin/sh mode and terminal signals
• Previous by thread: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• Next by thread: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]