Re: [PATCH 2/3] z3fold: remove redundant locking

2016-10-22 Thread Vitaly Wool
On Thu, Oct 20, 2016 at 10:15 PM, Dan Streetman wrote: > On Wed, Oct 19, 2016 at 12:35 PM, Vitaly Wool wrote: >> The per-pool z3fold spinlock should generally be taken only when >> a non-atomic pool variable is modified. There's no need to take it >> to

Re: [PATCH 2/3] z3fold: remove redundant locking

2016-10-22 Thread Vitaly Wool
On Thu, Oct 20, 2016 at 10:15 PM, Dan Streetman wrote: > On Wed, Oct 19, 2016 at 12:35 PM, Vitaly Wool wrote: >> The per-pool z3fold spinlock should generally be taken only when >> a non-atomic pool variable is modified. There's no need to take it >> to map/unmap an object. This patch introduces

Re: [PATCH 2/3] z3fold: remove redundant locking

2016-10-20 Thread Dan Streetman
On Wed, Oct 19, 2016 at 12:35 PM, Vitaly Wool wrote: > The per-pool z3fold spinlock should generally be taken only when > a non-atomic pool variable is modified. There's no need to take it > to map/unmap an object. This patch introduces per-page lock that > will be used

Re: [PATCH 2/3] z3fold: remove redundant locking

2016-10-20 Thread Dan Streetman
On Wed, Oct 19, 2016 at 12:35 PM, Vitaly Wool wrote: > The per-pool z3fold spinlock should generally be taken only when > a non-atomic pool variable is modified. There's no need to take it > to map/unmap an object. This patch introduces per-page lock that > will be used instead to protect

[PATCH 2/3] z3fold: remove redundant locking

2016-10-19 Thread Vitaly Wool
The per-pool z3fold spinlock should generally be taken only when a non-atomic pool variable is modified. There's no need to take it to map/unmap an object. This patch introduces per-page lock that will be used instead to protect per-page variables in map/unmap functions. Signed-off-by: Vitaly

[PATCH 2/3] z3fold: remove redundant locking

2016-10-19 Thread Vitaly Wool
The per-pool z3fold spinlock should generally be taken only when a non-atomic pool variable is modified. There's no need to take it to map/unmap an object. This patch introduces per-page lock that will be used instead to protect per-page variables in map/unmap functions. Signed-off-by: Vitaly

[PATCH 2/3] z3fold: remove redundant locking

2016-10-13 Thread Vitaly Wool
The per-pool z3fold spinlock should generally be taken only when a non-atomic pool variable is modified. There's no need to take it to map/unmap an object. Signed-off-by: Vitaly Wool --- mm/z3fold.c | 17 + 1 file changed, 5 insertions(+), 12 deletions(-)

[PATCH 2/3] z3fold: remove redundant locking

2016-10-13 Thread Vitaly Wool
The per-pool z3fold spinlock should generally be taken only when a non-atomic pool variable is modified. There's no need to take it to map/unmap an object. Signed-off-by: Vitaly Wool --- mm/z3fold.c | 17 + 1 file changed, 5 insertions(+), 12 deletions(-) diff --git