From: "Holden Karau" <holden@pigscanfly.ca>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: "Josef Sipek" <jsipek@fsl.cs.sunysb.edu>,
hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org,
holdenk@xandros.com, "akpm@osdl.org" <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1] fat: improve sync performance by grouping writes in fat_mirror_bhs [really unmangled]
Date: Fri, 27 Oct 2006 14:55:07 -0400 [thread overview]
Message-ID: <f46018bb0610271155kaccbf61p86b590a9c1580b06@mail.gmail.com> (raw)
In-Reply-To: <4540AA20.1090005@yahoo.com.au>
Based on some rather off-the cuff bench marking I've done I get around
a 5 to 10% performance improve over the stock 2.6.18.1 performance. As
the saying goes, there are lies, damn lies, and bench marks, so YMMV.
On 10/26/06, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Holden Karau wrote:
> > From: Holden Karau <holden@pigscanfly.ca> http://www.holdenkarau.com
> >
> > This is an attempt at improving fat_mirror_bhs in sync mode [namely it
> > writes all of the data for a backup block, and then blocks untill
> > finished]. The old behaviour would write & block in smaller chunks, so
> > this should be slightly faster. It also removes the fixme requesting
> > that it be fixed to behave this way :-)
> > Signed-off-by: Holden Karau <holden@pigscanfly.ca> http://www.holdenkarau.com
>
> So how much is performance improved?
>
> --
> SUSE Labs, Novell Inc.
> Send instant messages to your online friends http://au.messenger.yahoo.com
>
>
--
Cell: 613-276-1645
next prev parent reply other threads:[~2006-10-27 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 11:59 [PATCH 1/1] fat: improve sync performance by grouping writes in fat_mirror_bhs [really unmangled] Holden Karau
2006-10-26 12:29 ` Nick Piggin
2006-10-27 18:55 ` Holden Karau [this message]
2006-10-26 15:30 ` Jörn Engel
2006-10-27 18:56 ` Holden Karau
2006-10-27 21:01 ` Josef Sipek
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=f46018bb0610271155kaccbf61p86b590a9c1580b06@mail.gmail.com \
--to=holden@pigscanfly.ca \
--cc=akpm@osdl.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=holdenk@xandros.com \
--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;
as well as URLs for NNTP newsgroup(s).