From: Andrew Morton <akpm@zip.com.au>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>, ext2-devel@lists.sourceforge.net
Subject: [patch] speed up ext3 synchronous mounts
Date: Sun, 24 Mar 2002 13:50:16 -0800 [thread overview]
Message-ID: <3C9E4A18.7DDC68AB@zip.com.au> (raw)
Again, we don't need to sync indirects as we dirty them because
we run a commit if IS_SYNC(inode) prior to returning to the
caller of write(2).
Writing a 10 meg file in 0.1 meg chunks is sped up by, err,
a factor of fifty. That's a best case.
--- linux-2.4.18-pre8/fs/ext3/inode.c Tue Feb 5 00:33:05 2002
+++ linux-akpm/fs/ext3/inode.c Wed Feb 6 23:40:48 2002
@@ -581,8 +581,6 @@ static int ext3_alloc_branch(handle_t *h
parent = nr;
}
- if (IS_SYNC(inode))
- handle->h_sync = 1;
}
if (n == num)
return 0;
-
next reply other threads:[~2002-03-24 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 21:50 Andrew Morton [this message]
2002-03-25 23:01 ` [Ext2-devel] [patch] speed up ext3 synchronous mounts Stephen C. Tweedie
2002-03-27 19:07 ` Matthias Andree
2002-03-27 19:13 ` Ed Sweetman
2002-03-27 19:17 ` 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=3C9E4A18.7DDC68AB@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).