[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120416175534.GA5533@gmail.com>
Date: Tue, 17 Apr 2012 01:55:34 +0800
From: Zheng Liu <gnehzuil.liu@...il.com>
To: Allison Henderson <achender@...ux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Extent tree status asking
Hi Allison,
Currently I am trying to reduce the lock contention of direct I/O in ext4
because it is a bottleneck. A trivial idea is that a new fucntion is
defined to replace the generic_file_aio_write, which do some write
operations with acquiring i_data_sem lock in inode.
I know that you are trying to implement extent tree, and I have seen your patch
set '[PATCH] Rename delayed extents to status extents'. After extent tree is
made, the implementation of direct I/O without i_mutex and range lock is
straightforward and it is better than my trivial idea. I think that
maybe I can borrow you works. So could you please share me your schedule
and/or other information?
Last month on ext4 workshop, we discuss the extent tree, range lock and I/O
tree. Obviously, I/O tree is used to store I/O operations, which can track
delay allocation, do unwritten->written conversion and implement range lock.
It is very useful for ext4 and I am interested in this proposal. I know that
you have begun to do some works. So would you like to tell me the status of
extent tree? I don't know whether or not there has some things that I can be
involved. If you have some advices or there is something that I can help,
please let me know. Thank you and looking forward your reply.
Regards,
Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists