From: Allison Henderson <achender@linux.vnet.ibm.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Lukas Czerner <lczerner@redhat.com>
Subject: working on extent locks for i_mutex
Date: Thu, 12 Jan 2012 20:01:43 -0700 [thread overview]
Message-ID: <4F0F9E97.1090403@linux.vnet.ibm.com> (raw)
Hi All,
I know this is an old topic, but I am poking it again because I've had
some work items wrap up, and Im planning on picking up on this one
again. I am thinking about implementing extent locks to replace
i_mutex. So I just wanted to touch base with folks and see what people
are working on because I know there were some folks out there that were
thing about doing similar solutions.
A while ago I had done some investigation on where i_mutex is currently
used, so I did a review and updated my list. Only one thing had been
removed, but I will leave the list here since it was a while ago. Let
me know if anyone has been working on similar concept. Thx!
Allison
List of ext4 functions that lock i_mutex:
ext4_sync_file
ext4_fallocate
ext4_move_extents via two helper routines:
mext_inode_double_lock and mext_inode_double_unlock
ext4_ioctl (for the EXT4_IOC_SETFLAGS ioctl)
ext4_quota_write
ext4_llseek
ext4_end_io_work
ext4_ind_direct_IO (only while calling ext4_flush_completed_IO)
Functions called by vfs with i_mutex locked:
ext4_setattr
ext4_da_writepages
ext4_rmdir
ext4_unlink
ext4_symlink
ext4_link
ext4_rename
ext4_get_block
next reply other threads:[~2012-01-13 3:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 3:01 Allison Henderson [this message]
2012-01-13 4:01 ` working on extent locks for i_mutex Andreas Dilger
2012-01-13 20:50 ` Allison Henderson
2012-01-13 4:34 ` Dave Chinner
2012-01-13 4:34 ` Dave Chinner
2012-01-13 7:14 ` Tao Ma
2012-01-13 7:14 ` Tao Ma
2012-01-13 11:52 ` Dave Chinner
2012-01-13 11:52 ` Dave Chinner
2012-01-13 11:57 ` Tao Ma
2012-01-13 11:57 ` Tao Ma
2012-01-13 20:50 ` Allison Henderson
2012-01-13 20:50 ` Allison Henderson
2012-01-15 23:57 ` Dave Chinner
2012-01-15 23:57 ` Dave Chinner
2012-01-16 17:46 ` Allison Henderson
2012-01-18 12:02 ` Zheng Liu
2012-01-18 12:02 ` Zheng Liu
2012-01-19 21:16 ` Frank Mayhar
2012-01-19 21:16 ` Frank Mayhar
2012-01-20 2:26 ` Zheng Liu
2012-01-20 2:26 ` Zheng Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0F9E97.1090403@linux.vnet.ibm.com \
--to=achender@linux.vnet.ibm.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.