Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK
From: Linus Torvalds (torvalds@transmeta.com)
Date: Wed Sep 18 2002 - 12:16:26 EST
- Next message: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Previous message: Alan Cox: "Linux 2.4.20-pre7-ac1"
- In reply to: Rik van Riel: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Next in thread: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Reply: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Wed, 18 Sep 2002, Rik van Riel wrote:
>
> That's about 18 times the timeout for the NMI oopser and will cause
> people real trouble.
Where did this NMI oopser argument come from? get_pid() doesn't even
disable interrupts. And we hold the read lock, and other interrupts aren't
allowed to take the write lock anyway. If the NMI oopser triggers, then
something else is going on than get_pid().
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Next message: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Previous message: Alan Cox: "Linux 2.4.20-pre7-ac1"
- In reply to: Rik van Riel: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Next in thread: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Reply: Ingo Molnar: "Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
This archive was generated by hypermail 2b29
: Mon Sep 23 2002 - 22:00:23 EST