lkml.org 
[lkml]   [2015]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH, RFC 0/2] Recover some scalability for DAX
Date
Hi all,

Currently, i_mmap_lock is huge bottleneck for DAX scalability as we use in
place of lock_page().

This patchset tries to recover some scalability by introducing per-mapping
range-lock. The range-lock itself is implemented by Jan Kara on top of
interval tree. It looks not so cheap, by should scale better than
exclusive i_mmap_lock.

Any comments?

Jan Kara (1):
lib: Implement range locks

Kirill A. Shutemov (1):
dax: use range_lock instead of i_mmap_lock

drivers/gpu/drm/Kconfig | 1 -
drivers/gpu/drm/i915/Kconfig | 1 -
fs/dax.c | 30 +++++++++--------
fs/inode.c | 1 +
include/linux/fs.h | 2 ++
include/linux/range_lock.h | 51 +++++++++++++++++++++++++++++
lib/Kconfig | 14 --------
lib/Kconfig.debug | 1 -
lib/Makefile | 3 +-
lib/range_lock.c | 78 ++++++++++++++++++++++++++++++++++++++++++++
mm/memory.c | 35 +++++++++++++-------
mm/rmap.c | 1 +
12 files changed, 174 insertions(+), 44 deletions(-)
create mode 100644 include/linux/range_lock.h
create mode 100644 lib/range_lock.c

--
2.5.0



\
 
 \ /
  Last update: 2015-08-10 17:41    [W:0.115 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site