From: "Holden Karau" <holden@pigscanfly.ca>
To: "OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>
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: Tue, 31 Oct 2006 21:33:11 -0500 [thread overview]
Message-ID: <f46018bb0610311833x75001040md57341bc568a8902@mail.gmail.com> (raw)
In-Reply-To: <87odrst22f.fsf@duaron.myhome.or.jp>
Whoops, sorry about that. Yes it would improve performance on fat12 &
fat16 [although I haven't tested it with fat12]. What I meant by that
sentance is that, fat sync performance is pretty bad with or without
my patch, its just slightly less worse with my patch :-)
On 10/31/06, OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
> "Holden Karau" <holden@pigscanfly.ca> writes:
>
> > This patch is just meant to make fat32 sync performance better, not
> > necessarily make it usable for everyone [one step at a time and all
> > that].
>
> Sorry, I can't see your point. The FAT12 and FAT16 also have backup FAT.
> And the your patch didn't make performance better, right?
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>
--
Cell: 613-276-1645
prev parent reply other threads:[~2006-11-01 2:33 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
2006-10-31 20:54 ` Holden Karau
2006-11-01 0:58 ` OGAWA Hirofumi
2006-11-01 2:33 ` Holden Karau [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=f46018bb0610311833x75001040md57341bc568a8902@mail.gmail.com \
--to=holden@pigscanfly.ca \
--cc=akpm@osdl.org \
--cc=hirofumi@mail.parknet.co.jp \
--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
Powered by JetHome