From: "Stephen C. Tweedie" <sct@redhat.com>
To: Michael Marxmeier <mike@marxmeier.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, CMA <cma@mclink.it>,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: e2fs performance as function of block size
Date: Fri, 24 Nov 2000 13:11:16 +0000 [thread overview]
Message-ID: <20001124131116.C10362@redhat.com> (raw)
In-Reply-To: <E13yNlM-0005Q3-00@the-village.bc.nu> <3A1C487C.30BDFE9F@marxmeier.com>
In-Reply-To: <3A1C487C.30BDFE9F@marxmeier.com>; from mike@marxmeier.com on Wed, Nov 22, 2000 at 11:28:12PM +0100
Hi,
On Wed, Nov 22, 2000 at 11:28:12PM +0100, Michael Marxmeier wrote:
>
> If the files get somewhat bigger (eg. > 1G) having a bigger block
> size also greatly reduces the ext2 overhead. Especially fsync()
> used to be really bad on big file but choosing a bigger block
> size changed a lot.
2.4 fsync should be better, but still dependent on file size. The
O_SYNC patches I posted the other day give you an fsync which is
independent of file size.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-24 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 19:46 e2fs performance as function of block size CMA
2000-11-21 17:30 ` Reto Baettig
2000-11-21 23:34 ` Alan Cox
2000-11-22 0:06 ` Jeff V. Merkey
2000-11-22 0:27 ` Brian Pomerantz
2000-11-22 0:27 ` Alan Cox
2000-11-22 0:37 ` Jeff V. Merkey
2000-11-22 22:28 ` Michael Marxmeier
2000-11-24 13:11 ` Stephen C. Tweedie [this message]
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=20001124131116.C10362@redhat.com \
--to=sct@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cma@mclink.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@marxmeier.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.