From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: John Helms <john.helms@photomask.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, Trice Jim <Jim.Trice@photomask.com>,
Andmike@us.ibm.com
Subject: Re: bug (trouble?) report on high mem support
Date: Fri, 15 Mar 2002 21:44:24 -0800 [thread overview]
Message-ID: <687464031.1016228663@[10.10.2.3]> (raw)
In-Reply-To: <20020316.4343600@linux.local>
In-Reply-To: <20020316.4343600@linux.local>
> The readprofile output I sent earlier is pretty
> accurate. I performed the test right after a reboot
> to the enterprise (64GB mem) kernel with a profile=2
> boot option. I then ran our program, which reads in
> a 3.1GB file from an NFS mount, and outputs a 2.4GB file
> in another format to the same NFS mount. Networking
> is achieved through an IBM Gigabit fiber card with
> Intel e1000 chipset, which we have downloaded the
> latest source just to get it to work. But network
> throughput looks great. Other programs using the
> NFS mounts work fine, so I'm pretty sure it's not
> a network issue.
>
> The smp kernel (no 64GB mem support) completed the
> file conversion in 3.5 hours. Previous attempts
> with the enterprise kernel (64GB mem support) had
> to be aborted after 3 days and only started to write
> the converted file to disk by then. This application
> does not run multi-threaded, but we will have
> multiple users running the program on separate
> file conversions simultaneously. Hence the need
> for lots of memory.
>
> I guess the main question at this point is whether
> our hardware supports high memory, and then which
> patches or kernel upgrades can correct our problem.
> If we upgrade the entire kernel, which release
> would you recommend for a stable production machine
> with >4GB memory? If there are swap improvements,
> we also need whatever we can get in that area.
You mention "64Gb support" or "no 64Gb support" throughout
this - have you tried a kernel with 4Gb support? That'd
give you the HIGHMEM bounce buffering still. One step at a
time ;-)
M.
next prev parent reply other threads:[~2002-03-16 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:25 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
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 [this message]
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='687464031.1016228663@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=Andmike@us.ibm.com \
--cc=Jim.Trice@photomask.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john.helms@photomask.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®