diff options
author | Robin Holt <holt@sgi.com> | 2009-04-02 16:59:45 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-02 19:05:10 -0700 |
commit | e8c158bb313c1df421eab7dc4299cd39cbbf5895 (patch) | |
tree | 8a5f1d01e58d0e358b2b0c9407fc494912e83c27 /crypto | |
parent | 41d577aa35aa0504fe28b76a948908bdb7fbec81 (diff) | |
download | kernel_samsung_tuna-e8c158bb313c1df421eab7dc4299cd39cbbf5895.zip kernel_samsung_tuna-e8c158bb313c1df421eab7dc4299cd39cbbf5895.tar.gz kernel_samsung_tuna-e8c158bb313c1df421eab7dc4299cd39cbbf5895.tar.bz2 |
Factor out #ifdefs from kernel/spinlock.c to LOCK_CONTENDED_FLAGS
SGI has observed that on large systems, interrupts are not serviced for a
long period of time when waiting for a rwlock. The following patch series
re-enables irqs while waiting for the lock, resembling the code which is
already there for spinlocks.
I only made the ia64 version, because the patch adds some overhead to the
fast path. I assume there is currently no demand to have this for other
architectures, because the systems are not so large. Of course, the
possibility to implement raw_{read|write}_lock_flags for any architecture
is still there.
This patch:
The new macro LOCK_CONTENDED_FLAGS expands to the correct implementation
depending on the config options, so that IRQ's are re-enabled when
possible, but they remain disabled if CONFIG_LOCKDEP is set.
Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
Signed-off-by: Robin Holt <holt@sgi.com>
Cc: <linux-arch@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Luck, Tony" <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions