From: Mingming Cao <cmm@us.ibm.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Valerie Henson <val_henson@linux.intel.com>,
Andrew Morton <akpm@osdl.org>,
pbadari@gmail.com, linux-kernel@vger.kernel.org,
Ext2-devel@lists.sourceforge.net, arjan@linux.intel.com,
zach.brown@oracle.com
Subject: Re: [Ext2-devel] [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Fri, 24 Mar 2006 11:14:54 -0800 [thread overview]
Message-ID: <1143227694.4561.141.camel@localhost.localdomain> (raw)
In-Reply-To: <20060324185237.GB18020@thunk.org>
On Fri, 2006-03-24 at 13:52 -0500, Theodore Ts'o wrote:
> On Fri, Mar 24, 2006 at 06:32:39AM -0800, Valerie Henson wrote:
> > Note that ext3's habit of clearing indirect blocks on truncate would
> > break some things I want to do in the future. (Insert secret plans
> > here.)
>
> This is fixable, but it would require making the truncate code (even
> more) complicated.....
>
> - Ted
>
Andreas suggested to perform asynchronous unlink/truncate to reduce the
latency of truncating/unlink before. What's other options we discussed
before, I forget.
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Ext2-devel mailing list
> Ext2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ext2-devel
next prev parent reply other threads:[~2006-03-24 19:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 1:10 [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit] Valerie Henson
2006-03-22 8:40 ` Valerie Henson
2006-03-22 13:08 ` Alan Cox
2006-03-22 18:18 ` [Ext2-devel] " Mingming Cao
2006-03-22 18:16 ` [Ext2-devel] " Mingming Cao
[not found] ` <200603230011.53793.ioe-lkml@rameria.de>
2006-03-22 23:52 ` Mingming Cao
2006-03-22 19:09 ` Badari Pulavarty
2006-03-22 22:48 ` Valerie Henson
2006-03-23 1:55 ` Andrew Morton
2006-03-24 14:32 ` Valerie Henson
2006-03-24 15:35 ` Dave Kleikamp
2006-03-24 18:48 ` Andrew Morton
2006-03-24 19:13 ` Mingming Cao
2006-03-24 19:31 ` Andreas Dilger
2006-03-24 18:52 ` Theodore Ts'o
2006-03-24 19:14 ` Mingming Cao [this message]
2006-03-24 19:28 ` Andreas Dilger
2006-03-24 20:01 ` Theodore Ts'o
2006-03-24 21:00 ` Andreas Dilger
2006-03-24 21:39 ` Theodore Ts'o
2006-03-24 22:16 ` Andreas Dilger
2006-03-25 5:13 ` Suparna Bhattacharya
2006-03-25 17:38 ` Ben Pfaff
2006-03-24 20:52 ` [Ext2-devel] " Matthew Wilcox
2006-03-24 21:23 ` Andreas Dilger
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=1143227694.4561.141.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=tytso@mit.edu \
--cc=val_henson@linux.intel.com \
--cc=zach.brown@oracle.com \
/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