public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian C. Thomas" <bcthomas@nature.Berkeley.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: severe performance degradation on serverworks with high mem
Date: Thu, 18 Oct 2001 14:45:05 -0700	[thread overview]
Message-ID: <20011018144504.B134@nature.Berkeley.edu> (raw)
In-Reply-To: <20011018125714.A360@nature.Berkeley.edu>
In-Reply-To: <20011018125714.A360@nature.Berkeley.edu>

Hi

I don't know if this helps, but I seem to have stumbled onto a
possible "fix" for this...

With 64GB high memory enabled in kernel 2.4.12-ac3, and mtrr turned
on, I was able to see all 8GB RAM on my machine by using the old
'append="mem=8000M"' command in my lilo.conf file... AND WITH NO LOSS
OF PERFORMANCE!

Does that help anyone with defining where this problem is coming from?

BCT

____________________________
Brian C. Thomas
bcthomas@nature.berkeley.edu

On Thu, Oct 18, 2001 at 12:57:15PM -0700, Brian C. Thomas wrote:
> Hi
> 
> I have a Supermicro S2QR6 board, which has the "Serverworks serverset
> III HE" chipset.  (Also, i have 8GB RAM, 4 Xeon P3 700MHz processors,
> and an Adaptec Ultra160 SCSI system - aix7xxx, built onto the 
> motherboard)
> 
> In all the 2.4.x series kernels (even up to 2.4.12-ac3 or
> 2.4.13-pre4), as soon as the high memory, 64GB option is enabled, the
> server slows down to a crawl, with no load showing.  (A "crawl"
> example is a kernel recompile time going from ~5 min to >2 hr!)
> 
> I have tried numerous kernel config options, removing scsi support,
> networking, and have narrowed the problem down to the serverworks
> chipset- on a SC440NX mb, also with 8GB and everything else in the
> system, all the new kernels work with no slowdown.
> 
> I've tried...
> kernels: 2.4.1, 2.4.3, 2.4.5, 2.4.7-ac9, 2.4.9, 2.4.12 (-pre4, -ac3)
> with and w/o mtrr support kernel config
> 
> Any ideas?
> 
> Thanks,
> 
> BCT
> 
> ____________________________
> Brian C. Thomas
> bcthomas@nature.berkeley.edu
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-10-18 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 19:57 severe performance degradation on serverworks with high mem Brian C. Thomas
2001-10-18 21:45 ` Brian C. Thomas [this message]
2001-10-18 23:01   ` Mike Fedyk
2001-10-19  7:24   ` Eric W. Biederman

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=20011018144504.B134@nature.Berkeley.edu \
    --to=bcthomas@nature.berkeley.edu \
    --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