From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Alain Tesio <alain@onesite.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HIGHMEM=4G slows down ps2pdf with 2.4.28
Date: Mon, 6 Dec 2004 16:41:18 -0200 [thread overview]
Message-ID: <20041206184118.GA2282@dmt.cyclades> (raw)
In-Reply-To: <20041203215819.15bab008@alain>
On Fri, Dec 03, 2004 at 09:58:19PM +0100, Alain Tesio wrote:
> On Thu, 2 Dec 2004 17:08:15 -0200
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
>
> > On Wed, Dec 01, 2004 at 11:25:22PM +0100, Alain Tesio wrote:
> > > Hi,
> > >
> > > With a 2.4.28 kernel, 1.5 Go RAM and nothing exotic, everything works fine
> > > with CONFIG_HIGHMEM4G and CONFIG_HIGHMEM=y except that
> > > ps2pdf is about 30 times slower
>
> > How does /proc/mtrr look like?
> >
> > Maybe some of your memory is configured as uncacheable.
>
> reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
> reg01: base=0x40000000 (1024MB), size= 256MB: write-back, count=1
> reg02: base=0x50000000 (1280MB), size= 128MB: write-back, count=1
> reg03: base=0x58000000 (1408MB), size= 64MB: write-back, count=1
> reg04: base=0x5c000000 (1472MB), size= 32MB: write-back, count=1
> reg05: base=0x5e000000 (1504MB), size= 16MB: write-back, count=1
>
> I don't think that the hosting company played with the bios settings,
> and I don't do anything special with memory.
Alain,
All memory is correctly configured in MTRR it seems (all of it is write-back cacheable).
Do you have CONFIG_HIGHIO=y ? That might help a lot. The kernel has to use
bounce buffers for IO otherwise.
next prev parent reply other threads:[~2004-12-07 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 22:25 HIGHMEM=4G slows down ps2pdf with 2.4.28 Alain Tesio
2004-12-02 19:08 ` Marcelo Tosatti
2004-12-03 20:58 ` Alain Tesio
2004-12-06 18:41 ` Marcelo Tosatti [this message]
2004-12-06 19:43 ` Marcelo Tosatti
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=20041206184118.GA2282@dmt.cyclades \
--to=marcelo.tosatti@cyclades.com \
--cc=alain@onesite.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.