public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Tsukamoto <at541@columbia.edu>
To: szonyi calin <caszonyi@yahoo.com>
Cc: linux-kernel@vger.kernel.org,
	Hirokazu Takahashi <taka@valinux.co.jp>, Andi Kleen <ak@suse.de>
Subject: Re: Performance improvement with Akira Tsukamoto's Athlon copy_user patch
Date: Tue, 19 Nov 2002 13:23:40 -0500	[thread overview]
Message-ID: <20021119132332.545D.AT541@columbia.edu> (raw)
In-Reply-To: <20021119173416.16110.qmail@web40604.mail.yahoo.com>

Hi Calin,

> 2.5.47 with copy user patch
> 
> /dev/hda:
>  Timing buffer-cache reads:   128 MB in  0.71 seconds =180.28 MB/sec
>  Timing buffered disk reads:  64 MB in  4.06 seconds = 15.78 MB/sec
> 
> 
> vanila 2.5.47
> 
> /dev/hda:
>  Timing buffer-cache reads:   128 MB in  1.09 seconds =117.32 MB/sec
>  Timing buffered disk reads:  64 MB in  4.05 seconds = 15.78 MB/sec

Thank you for trying, 
I also been using for compiling kernel for several days,
but, as Andi mentioned, currently the aki_copy is *dangerous* 
when any processes/threads ara using fpu register.

I read the code of laze FPU state saving and confirmed that 
if the function does not generate exception than
'kernel_fpu_begin/end()' should assure fpu safe inside kernel.

However, it is not enough where exception could rise, as Takahashi
mentioned.

I also have benchmark for small buffer which is enough to fit in cache
which I would like to show that aki_copy does perform well for this 
circumstances. 
But I have something urgent todo(homework :)) and I will come back to it
as soon as possible.

Thank you,

Akira Tsukamoto

On Tue, 19 Nov 2002 18:34:16 +0100 (CET)
szonyi calin <caszonyi@yahoo.com> mentioned:

> Hello everybody 
> 
> I patched yesterday the 2.5.47 vanilla kernel with Akira
>  Tsukamoto's Athlon copy_user patch and tried a 
> hdparm -tT /dev/hda 
> 
> The results (atached) are impressive compared with both the 
> vanilla 2.5.47 kernel and the 2.4.19 with ck-rl5 patches (from
>  colivas)
> 
> Bye
> 
> Calin
> 
> 
> 
> =====
> --
> A mouse is a device used to point at 
> the xterm you want to type in.
> Kim Alm on a.s.r.
> 
> ___________________________________________________________
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran軋is !
> Yahoo! Mail : http://fr.mail.yahoo.com

-- 
Akira Tsukamoto <akira-t@suna-asobi.com, at541@columbia.edu>



  parent reply	other threads:[~2002-11-19 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 17:34 Performance improvement with Akira Tsukamoto's Athlon copy_user patch szonyi calin
2002-11-19 18:20 ` Akira Tsukamoto
2002-11-19 18:23 ` Akira Tsukamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 19:18 Manfred Spraul
2002-11-20  6:03 ` Akira Tsukamoto

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=20021119132332.545D.AT541@columbia.edu \
    --to=at541@columbia.edu \
    --cc=ak@suse.de \
    --cc=caszonyi@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox