Re: [PATCH v2 05/13] rwsem: simplify rwsem_down_write_failed

2013-03-28 Thread Rik van Riel
On 03/15/2013 06:54 AM, Michel Lespinasse wrote: When waking writers, we never grant them the lock - instead, they have to acquire it themselves when they run, and remove themselves from the wait_list when they succeed. As a result, we can do a few simplifications in rwsem_down_write_failed():

Re: [PATCH v2 05/13] rwsem: simplify rwsem_down_write_failed

2013-03-28 Thread Rik van Riel
On 03/15/2013 06:54 AM, Michel Lespinasse wrote: When waking writers, we never grant them the lock - instead, they have to acquire it themselves when they run, and remove themselves from the wait_list when they succeed. As a result, we can do a few simplifications in rwsem_down_write_failed():

[PATCH v2 05/13] rwsem: simplify rwsem_down_write_failed

2013-03-15 Thread Michel Lespinasse
When waking writers, we never grant them the lock - instead, they have to acquire it themselves when they run, and remove themselves from the wait_list when they succeed. As a result, we can do a few simplifications in rwsem_down_write_failed(): - We don't need to check for !waiter.task since

[PATCH v2 05/13] rwsem: simplify rwsem_down_write_failed

2013-03-15 Thread Michel Lespinasse
When waking writers, we never grant them the lock - instead, they have to acquire it themselves when they run, and remove themselves from the wait_list when they succeed. As a result, we can do a few simplifications in rwsem_down_write_failed(): - We don't need to check for !waiter.task since