All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>,
	linux-kernel@vger.kernel.org, janetmor@us.ibm.com
Subject: Re: [patch] readv/writev rework
Date: Fri, 13 Sep 2002 21:54:09 -0700	[thread overview]
Message-ID: <3D82C0F1.8733207D@digeo.com> (raw)
In-Reply-To: 3D815C04.A08CB5D9@digeo.com

Andrew Morton wrote:
> 
> ...
> walk this linked list, writing the lines out.  The input was
> `cat linux/kernel/*.c > inputfile' and the output was written
> 1000 times (300 megs).  Benched four different ways of writing the
> output:
> 
>                     2.5.34         2.5.34-mm2         2.5.34-mm2-taka
> 
> write                 54s             54s                   55s
> fwrite                12.8s          12.8s                 12.7s
> fwrite_unlocked       11.6s          11.6s                 11.5s
> writev                39s            33.4s                 15.8s
> 
> So Janet's patch made a 15% improvement with this test.  Yours
> dropped it 50% again.
> 

I've retested with your latest patch.

                   2.5.34-mm4-taka2
write                  55.543
fwrite                 12.625
fwrite_unlocked        11.389
writev                  9.219

So that's another 70% speedup on top of yesterday's 100%, and kernel
beats glibc ;)

  reply	other threads:[~2002-09-14  4:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  8:30 [patch] readv/writev rework Andrew Morton
2002-09-12 13:00 ` Hirokazu Takahashi
2002-09-12 18:47   ` Andrew Morton
2002-09-13  1:18     ` Hirokazu Takahashi
2002-09-13  3:31       ` Andrew Morton
2002-09-14  4:54         ` Andrew Morton [this message]
2002-09-14  7:39           ` Hirokazu Takahashi
2002-09-13  7:22     ` Hirokazu Takahashi
2002-09-13  8:29       ` Andrew Morton
2002-09-13  8:26         ` Hirokazu Takahashi
2002-09-13  9:23         ` Hirokazu Takahashi
2002-09-13 17:43           ` Andrew Morton

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=3D82C0F1.8733207D@digeo.com \
    --to=akpm@digeo.com \
    --cc=janetmor@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=taka@valinux.co.jp \
    /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.