Messages in this thread | | | Date | Sun, 12 Sep 2004 15:02:13 +1000 | From | Nick Piggin <> | Subject | Re: [PATCH] Yielding processor resources during lock contention |
| |
Zwane Mwaikambo wrote:
>>If yes, then shouldn't your lock be a blocking lock anyway? > > > We just happen to allow preemption since we know we're at an upper level > lock, so we may as well not disable preemption during contention. It > wouldn't be as straightforward to switch to a blocking lock. >
OK that sounds alight.
If it is a "I'm going to be spinning for ages, so schedule me off *now*" then I think it is wrong... but if it just allows you to keep the hypervisor preemption turned on, then fine. - 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/
| |