From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Holden Karau" <holden@pigscanfly.ca>
Cc: "Holden Karau" <holdenk@xandros.com>,
"Josef Sipek" <jsipek@fsl.cs.sunysb.edu>,
linux-kernel@vger.kernel.org, "akpm@osdl.org" <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org,
"Nick Piggin" <nickpiggin@yahoo.com.au>,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: [PATCH 1/1] fat: improve sync performance by grouping writes revised
Date: Wed, 01 Nov 2006 05:23:58 +0900 [thread overview]
Message-ID: <87slh4tesh.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <f46018bb0610311046t6aa969ccy60a2020f7e5a0ed9@mail.gmail.com> (Holden Karau's message of "Tue\, 31 Oct 2006 13\:46\:46 -0500")
"Holden Karau" <holden@pigscanfly.ca> writes:
> The performance increase is pretty small. Using an old external dirve
> I had lying around I got:
> diff -y stock/10k modified/10k
> 10240+0 records in | 1024+0
> records in
> 10240+0 records out | 1024+0
> records out
> 5242880 bytes transferred in 18.280922 seconds (286795 bytes/ | 524288
> bytes transferred in 1.824985 seconds (287283 bytes/se
1024 records out 1.824985 seconds. Is there decrease case? I assume
the result is same. So, we would need different approach.
> diff -y stock/1k modified/1k
> 1024+0 records in 1024+0
> records in
> 1024+0 records out 1024+0
> records out
> 524288 bytes transferred in 1.777250 seconds (295000 bytes/se | 524288
> bytes transferred in 1.764748 seconds (297089 bytes/se
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2006-10-31 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 15:03 Holden Karau
2006-10-31 16:28 ` Matthew Wilcox
2006-10-31 16:46 ` Holden Karau
2006-11-01 3:10 ` Holden Karau
2006-11-01 13:50 ` Matthew Wilcox
2006-10-31 16:30 ` Jörn Engel
2006-10-31 18:10 ` Holden Karau
2006-10-31 16:54 ` OGAWA Hirofumi
2006-10-31 18:46 ` Holden Karau
2006-10-31 20:23 ` OGAWA Hirofumi [this message]
2006-10-31 20:54 ` Holden Karau
2006-11-01 0:58 ` OGAWA Hirofumi
2006-11-01 2:33 ` Holden Karau
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=87slh4tesh.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@osdl.org \
--cc=holden@pigscanfly.ca \
--cc=holdenk@xandros.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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®