From: Jan Kara <jack@suse.cz>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, linux-ext4@vger.kernel.org
Subject: Re: ext4 lock ordering patch
Date: Tue, 27 May 2008 14:13:37 +0200 [thread overview]
Message-ID: <20080527121337.GF5178@duck.suse.cz> (raw)
In-Reply-To: <20080526175109.GA14718@skywalker>
On Mon 26-05-08 23:21:09, Aneesh Kumar K.V wrote:
> On Mon, May 26, 2008 at 07:34:52PM +0200, Jan Kara wrote:
> > Hi Mingming,
> >
> > I've noticed you removed the patch reversing locking order of page lock
> > and transaction start from ext4 patch queue. Was this because of that
> > reported performance problem or for some other reason? As far as I've
> > understood that problem has been just in the patch fixing the delalloc mode
> > part so just removing that patch would be enough AFAICT.
> > Anyway, the problem is I have now ordered mode rewrite for JBD2/ext4
> > which depends on this patch so the question is how to proceed... Should we
> > first fix that delalloc problem (are you looking into that?) or do we merge
> > all the changes and then fixup the delalloc code?
> >
> That was due to delalloc interaction with locking order change patches.
What kind of interaction do you mean? My patch actually didn't handle
delalloc at all - Mingming had a patch to workaround that.
> I am right now testing some changes for delalloc. But I still have file
> system hang with fsstress. So I haven't posted the latest changes yet.
OK and do these changes count with reversion of the locking order or
not? Because my feeling when I last looked at delalloc was that with the
lock-ordering reversed it would be better to do da_writepages() and similar
stuff differently...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2008-05-27 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 17:34 ext4 lock ordering patch Jan Kara
2008-05-26 17:51 ` Aneesh Kumar K.V
2008-05-27 12:13 ` Jan Kara [this message]
2008-05-28 21:08 ` Mingming Cao
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=20080527121337.GF5178@duck.suse.cz \
--to=jack@suse.cz \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox