All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org,
	sct@redhat.com
Subject: Re: [RFC] ext3 writepages for writeback mode
Date: Fri, 11 Feb 2005 17:00:36 -0800	[thread overview]
Message-ID: <20050211170036.617afa48.akpm@osdl.org> (raw)
In-Reply-To: <1108169488.20053.1241.camel@dyn318077bld.beaverton.ibm.com>

Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> BEFORE: (without writepages support)
>                                                                                                        
> elm3b29:/mnt # touch file
> elm3b29:/mnt # time /tmp/writer file
> real    0m23.746s user    0m0.000s sys     0m5.020s (allocation)
> elm3b29:/mnt # time /tmp/writer file
> real    0m20.950s user    0m0.001s sys     0m2.278s (no alloc)
> elm3b29:/mnt # time /tmp/writer file
> real    0m21.030s user    0m0.001s sys     0m2.254s (no alloc)
> elm3b29:/mnt # time /tmp/writer file
> real    0m20.577s user    0m0.001s sys     0m2.184s (no alloc)
>                                                                                                        
> ====
> AFTER: (with writepages support)
>                                                                                                        
> elm3b29:/mnt # touch file
> elm3b29:/mnt # time /tmp/writer file
> real    0m23.230s user    0m0.001s sys     0m4.132s (allocation)
> elm3b29:/mnt # time /tmp/writer file
> real    0m20.175s user    0m0.004s sys     0m1.756s (no alloc)
> elm3b29:/mnt # time /tmp/writer file
> real    0m20.368s user    0m0.001s sys     0m1.696s (no alloc)
> elm3b29:/mnt # time /tmp/writer file
> real    0m20.626s user    0m0.002s sys     0m1.763s (no alloc)

Holy cow.  I'm shocked.

There's no system CPU time involved, and the user CPU time didn't change. 
We must be getting better I/O scheduling for some reason.  I wonder what it
is?

That, or we're forgetting to write something ;)

What journalling mode were you using?
What I/O scheduler?
What sort of disk system?

  reply	other threads:[~2005-02-12  0:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  1:31 [RFC] ext3 writepages for writeback mode Badari Pulavarty
2005-02-11  1:53 ` Andrew Morton
2005-02-11  3:06   ` Badari Pulavarty
2005-02-11 23:29   ` Badari Pulavarty
2005-02-11 23:58     ` Andrew Morton
2005-02-12  0:09       ` Badari Pulavarty
2005-02-14 20:02         ` Sonny Rao
2005-02-14 20:22           ` [Ext2-devel] " Sonny Rao
2005-02-12  0:51       ` Badari Pulavarty
2005-02-12  1:00         ` Andrew Morton [this message]
2005-02-12  1:55           ` Badari Pulavarty
2005-02-12 12:20         ` [Ext2-devel] " Alex Tomas
2005-02-12 18:47           ` Badari Pulavarty
2005-02-12 21:43             ` Alex Tomas
2005-02-12 23:26           ` Badari Pulavarty
2005-02-12 23:29             ` Alex Tomas
2005-02-14 15:58               ` Badari Pulavarty
2005-02-14 16:34                 ` Alex Tomas
2005-02-14 16:50 ` Thiago Rondon
2005-02-14 18:08   ` Badari Pulavarty

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=20050211170036.617afa48.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=sct@redhat.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.