From: John Helms <john.helms@photomask.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Jim.Trice@photomask.com (Trice Jim),
Martin.Bligh@us.ibm.com
Subject: Re: bug (trouble?) report on high mem support
Date: Fri, 15 Mar 2002 20:32:46 GMT [thread overview]
Message-ID: <20020315.20324600@linux.local> (raw)
In-Reply-To: <E16lyLG-0004Zo-00@the-village.bc.nu>
In-Reply-To: <E16lyLG-0004Zo-00@the-village.bc.nu>
Alan,
Ok, how do I go about determining that? The machine
I have is a brand-spankin' new IBM x-series 350 with
4 900MHz Xeon processors. The system bios can
recognize all of the 16320MB of memory at startup.
If those patches work, it will save our butts as
we have a major conversion project that hinges on
this.
Thanks,
jwh
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 3/15/02, 2:30:22 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote regarding
Re: bug (trouble?) report on high mem support:
> > Here is a top output. We have 16Gb of ram.
> > I have also tried a 2.4.9-31 enterprise=20
> > kernel rpm from RedHat with the same=20
> > results.
> Ok that would make sense. Next question is do you have an I/O controller
> that can use all the 64bit address space on the PCI bus ?
> What is happening is that you are using a lot of CPU copying buffers down
> into lower memory to transfer to/from disk - as well probably as that
> causing a lot of competition for low memory. If your I/O controller can
hit
> the full 64bit space there are some rather nice test patches that should
> completely obliterate the problem.
> Alan
next prev parent reply other threads:[~2002-03-15 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:25 bug (trouble?) report on high mem support John Helms
2002-03-15 20:05 ` Alan Cox
2002-03-15 20:07 ` John Helms
2002-03-15 20:30 ` Alan Cox
2002-03-15 20:32 ` John Helms [this message]
2002-03-15 23:37 ` Mike Anderson
2002-03-15 23:38 ` Randy.Dunlap
2002-03-16 0:02 ` Martin J. Bligh
2002-03-16 4:34 ` John Helms
2002-03-16 5:44 ` Martin J. Bligh
2002-03-18 21:45 ` Randy.Dunlap
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=20020315.20324600@linux.local \
--to=john.helms@photomask.com \
--cc=Jim.Trice@photomask.com \
--cc=Martin.Bligh@us.ibm.com \
--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