lkml.org 
[lkml]   [2013]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/6 RFC] Mapping range lock
On Thu, Jan 31, 2013 at 04:07:57PM -0800, Andrew Morton wrote:
[snip]
> > c) i_mutex doesn't allow any paralellism of operations using it and some
> > filesystems workaround this for specific cases (e.g. DIO reads). Using
> > range locking allows for concurrent operations (e.g. writes, DIO) on
> > different parts of the file. Of course, range locking itself isn't
> > enough to make the parallelism possible. Filesystems still have to
> > somehow deal with the concurrency when manipulating inode allocation
> > data. But the range locking at least provides a common VFS mechanism for
> > serialization VFS itself needs and it's upto each filesystem to
> > serialize more if it needs to.
>
> That would be useful to end-users, but I'm having trouble predicting
> *how* useful.

Hello Andrew,

I believe this would be useful for the end-user, at least for dio user, e.g.
database. Now when we want to issue a direct io, i_mutex will serialize
concurrent reader/writer. Some filesystems (xfs and ext4) try not to take
this locking in some conditions to improve the performance, especially for the
latency, because we don't need to wait on this locking. But there are still
some cases that need to take it. So range locking can make us reduce the
contention as far as possible.

Regards,
- Zheng


\
 
 \ /
  Last update: 2013-02-04 11:02    [W:1.320 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site