From: Andreas Dilger <adilger@clusterfs.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: [RFC/RFT] [PATCH] EXT3: Retry allocation after journal commit
Date: Fri, 14 May 2004 11:48:37 -0600 [thread overview]
Message-ID: <20040514174837.GF18086@schnapps.adilger.int> (raw)
In-Reply-To: <20040513214922.24639ae3.akpm@osdl.org>
On May 13, 2004 21:49 -0700, Andrew Morton wrote:
> Andreas's patch is a bit sneaky: it simply sets ->h_sync on the current
> transaction then does journal_stop(). I think your patch can do the same
> thing?
Well, actually my patch just waited on the _previous_ transaction to commit
(which can be done anywhere without retrying the operation) and then set
h_sync on the _current_ transaction so that as soon as the current operations
are completed it will also be committed and the blocks released. One can't
of course arbitrarily call journal_stop() or that breaks the transaction
atomicity.
For 99.9% of cases this should be sufficient and doesn't involve changing
the code everywhere - only in ext3_new_block(). Also, Ted's approach
of retrying the operations "outside" the transaction won't work if there
are nested journal transactions being done - those will hold the transaction
open so doing journal_stop/journal_start doesn't really accomplish anything.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2004-05-14 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 0:42 Theodore Ts'o
2004-05-14 2:53 ` Andrew Morton
2004-05-14 4:37 ` [Ext2-devel] " Theodore Ts'o
2004-05-14 4:49 ` Andrew Morton
2004-05-14 17:48 ` Andreas Dilger [this message]
2004-05-14 19:59 ` Theodore Ts'o
2004-05-14 21:06 ` Andreas Dilger
2004-05-15 13:18 ` Theodore Ts'o
2004-05-19 22:04 ` question about ext3_find_goal with reservation Mingming Cao
2004-05-19 22:52 ` Andrew Morton
2004-05-20 1:04 ` [Ext2-devel] " 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=20040514174837.GF18086@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®