On 03/15/2013 06:54 AM, Michel Lespinasse wrote:
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse
Acked-by: Rik van Riel
--
To
On Fri, 2013-03-15 at 03:54 -0700, Michel Lespinasse wrote:
> Using rwsem_atomic_update to try stealing the write lock forced us to
> undo the adjustment in the failure path. We can have simpler and faster
> code by using cmpxchg instead.
>
> Signed-off-by: Michel Lespinasse
>
> ---
>
On 03/15/2013 06:54 AM, Michel Lespinasse wrote:
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse wal...@google.com
Acked-by: Rik van
On Fri, 2013-03-15 at 03:54 -0700, Michel Lespinasse wrote:
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse wal...@google.com
---
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse
---
lib/rwsem.c | 26 ++
1 file changed, 6 insertions(+), 20
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse wal...@google.com
---
lib/rwsem.c | 26 ++
1 file changed, 6
6 matches
Mail list logo