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

* Nick Piggin <[email protected]> wrote:

> 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.

curious, do you have any (relatively-) simple to run testcase that 
clearly shows the "scalability issues" you mention above, when going 
from rwlocks to spinlocks? I'd like to give it a try on an 8-way box.

	Ingo
-
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/

---

• Follow-Ups:
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Nick Piggin <[email protected]>

• 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: USB/hal: USB open() broken? (USB CD burner underruns, USB HDD hard resets)
• Next by Date: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
• 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]