public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI-SCI Drivers v1.1-7 released
Date: Wed, 7 Feb 2001 11:19:00 -0700	[thread overview]
Message-ID: <20010207111900.E27089@vger.timpanogas.org> (raw)
In-Reply-To: <20010206190624.C23960@vger.timpanogas.org> <E14QQoH-0008CH-00@the-village.bc.nu>
In-Reply-To: <E14QQoH-0008CH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 07, 2001 at 09:22:43AM +0000

On Wed, Feb 07, 2001 at 09:22:43AM +0000, Alan Cox wrote:
> > kernel on gcc 2.91, running SCI benchmarks, then compiling on RedHat 
> > 7.1 (Fischer) with gcc 2.96, the 2.96 build DROPPED 30% in throughput
> > from the gcc 2.91 compiled version on the identical SAME 2.4.1 
> > source tree. 
> 
> 30% is too big to be caused by a compiler. Way too big.I suggest you review
> your code.

I went back and looked at what was being generated.  for the sci copy testing,
the MTRR settings are changed to enable write combining, which causes the 
PCI bus to burst data whenever the SCI mapped page hits a cache line 
during copy operations -- speeds it up by 20-30% over DMA methods using 
the same adapters.  

I looked into this, and discovered that the gcc 2.96 compiler turned my 
rep movsd code into a rep movsb (???) with some evil looking C++ style 
jump table in the assembler code that jumped all over the place, which 
is what caused the performance test numbers to drop.  DMA numbers were 
the same on both kernels with the dma_test benchmark -- they were not 
with the sci_bench2 program.   

They deviated by 30%, indicating that my MTRR write combining optimization
was not working properly in sci copy mode.  

Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-07 17:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  1:25 PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
2001-02-07  2:06 ` Jeff V. Merkey
2001-02-07  2:07   ` [OT] " Gregory Maxwell
2001-02-07 18:08     ` Jeff V. Merkey
2001-02-07 17:32       ` Jakub Jelinek
2001-02-07 18:31         ` Jeff V. Merkey
2001-02-07 18:37           ` Tim Wright
2001-02-07 20:14             ` Jeff V. Merkey
2001-02-07 19:22               ` Alan Cox
2001-02-07 20:24                 ` Jeff V. Merkey
2001-02-07 20:35                   ` PCI-SCI Build Problems on RedHat 7.1 Jeff V. Merkey
2001-02-07 19:52                     ` Larry
2001-02-07  9:01   ` PCI-SCI Drivers v1.1-7 released David Howells
2001-02-07 18:10     ` Jeff V. Merkey
2001-02-07  9:22   ` Alan Cox
2001-02-07 18:19     ` Jeff V. Merkey [this message]
2001-02-07 19:06       ` Alan Cox
2001-02-07 20:03         ` Jeff V. Merkey
2001-02-07 19:12           ` Alan Cox
2001-02-07  9:15 ` Alan Cox
2001-02-07 18:13   ` Jeff V. Merkey
2001-02-07 19:02     ` Alan Cox
2001-02-07 20:02       ` Jeff V. Merkey

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=20010207111900.E27089@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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