From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.4 PATCH: gcc 3.3 support
Date: Thu, 07 Aug 2003 02:51:19 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106022476310446@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106018469231198@msgid-missing>
On Wed, Aug 06, 2003 at 09:59:34AM -0600, Bjorn Helgaas wrote:
> On Wednesday 06 August 2003 9:44 am, H. J. Lu wrote:
> > This is the patch backed ported from 2.6 kernel. However, I got
> >
> > # modprobe xor
> > raid5: measuring checksumming speed
> > ia64 : 81.920 MB/sec
This number was under heavy load. I got
Aug 6 09:03:38 gnu-2 kernel: raid5: measuring checksumming speed
Aug 6 09:03:38 gnu-2 kernel: ia64 : 98.304 MB/sec
Aug 6 09:03:38 gnu-2 kernel: raid5: using function: ia64 (98.304 MB/sec)
with 2.4 kernel when machine was idle.
> >
> > The old one I got
> >
> > # modprobe xor
> > raid5: measuring checksumming speed
> > 8regs : 1769.472 MB/sec
> > 8regs_prefetch: 1753.088 MB/sec
> > 32regs : 2064.384 MB/sec
> > 32regs_prefetch: 2064.384 MB/sec
> > ia64 : 2441.216 MB/sec
> > raid5: using function: ia64 (2441.216 MB/sec)
> >
> > It is very strange.
>
> That *is* very strange. I'll wait to apply the patch until we understand
> what's happening. Have you tried the 2.6 kernel to see what speeds it
> measures?
With 2.6.0-test2, I got
raid5: measuring checksumming speed
ia64 : 98.304 MB/sec
raid5: using function: ia64 (98.304 MB/sec)
It looks like a separate asm file hurt the number very badly.
H.J.
next prev parent reply other threads:[~2003-08-07 2:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 15:44 2.4 PATCH: gcc 3.3 support H. J. Lu
2003-08-06 15:59 ` Bjorn Helgaas
2003-08-06 16:01 ` H. J. Lu
2003-08-07 2:51 ` H. J. Lu [this message]
2003-08-07 4:53 ` David Mosberger
2003-08-07 5:57 ` H. J. Lu
2003-08-07 17:28 ` H. J. Lu
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=marc-linux-ia64-106022476310446@msgid-missing \
--to=hjl@lucon.org \
--cc=linux-ia64@vger.kernel.org \
/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