From: Joel Becker <jlbec@evilplan.org>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Ted Ts'o <tytso@mit.edu>
Subject: Re: i_mutex questions
Date: Tue, 13 Sep 2011 17:05:53 -0700 [thread overview]
Message-ID: <20110914000553.GA8761@noexit.corp.google.com> (raw)
In-Reply-To: <4E6FD4F0.4000901@linux.vnet.ibm.com>
On Tue, Sep 13, 2011 at 03:10:56PM -0700, Allison Henderson wrote:
> Well, I actually already had a patch that was trying to use i_mutex
> to solve this ([PATCH 4/6 v7] ext4: Lock i_mutex for punch hole).
> But we decided not to apply it because of plans to reduce the usage
> of i_mutex in the ext4 code. So I've been trying to figure out a
> different way to solve this, but so far I haven't had a whole lot of
> luck finding a solution that doesn't involve introducing a new
> locking mechanism. So I wanted to check back here for more details
> on what the plan for i_mutex is so I dont conflict with anything
> that might already be going on. :)
Sure ;-) If you find another mechanism that reduces contention
but still plays well with read/write et al, please let us all know.
Getting i_mutex out of read/write would be interesting.
Joel
--
"A narcissist is someone better looking than you are."
- Gore Vidal
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-09-14 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 18:33 i_mutex questions Allison Henderson
2011-09-13 19:02 ` Joel Becker
2011-09-13 22:10 ` Allison Henderson
2011-09-14 0:05 ` Joel Becker [this message]
2011-09-14 1:29 ` Yongqiang Yang
2011-09-14 4:23 ` Andreas Dilger
2011-09-14 18:36 ` Allison Henderson
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=20110914000553.GA8761@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--cc=achender@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).