Re: [PATCH/RESEND v2 4/5] z3fold: use per-page spinlock

2017-01-11 Thread Dan Streetman
On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: > Most of z3fold operations are in-page, such as modifying z3fold page > header or moving z3fold objects within a page. Taking per-pool spinlock > to protect per-page objects is therefore suboptimal, and the idea of >

Re: [PATCH/RESEND v2 4/5] z3fold: use per-page spinlock

2017-01-11 Thread Dan Streetman
On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: > Most of z3fold operations are in-page, such as modifying z3fold page > header or moving z3fold objects within a page. Taking per-pool spinlock > to protect per-page objects is therefore suboptimal, and the idea of > having a per-page

[PATCH/RESEND v2 4/5] z3fold: use per-page spinlock

2017-01-11 Thread Vitaly Wool
Most of z3fold operations are in-page, such as modifying z3fold page header or moving z3fold objects within a page. Taking per-pool spinlock to protect per-page objects is therefore suboptimal, and the idea of having a per-page spinlock (or rwlock) has been around for some time. This patch

[PATCH/RESEND v2 4/5] z3fold: use per-page spinlock

2017-01-11 Thread Vitaly Wool
Most of z3fold operations are in-page, such as modifying z3fold page header or moving z3fold objects within a page. Taking per-pool spinlock to protect per-page objects is therefore suboptimal, and the idea of having a per-page spinlock (or rwlock) has been around for some time. This patch