All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Klaus Meyer <k.meyer@m3its.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: highmem=system killer, 2.2.17=performance killer ?
Date: Tue, 15 Jan 2002 16:00:18 +0100	[thread overview]
Message-ID: <20020115160018.18793569.skraw@ithnet.com> (raw)
In-Reply-To: <3C439E6D.B2B8C5B8@m3its.de>
In-Reply-To: <3C439E6D.B2B8C5B8@m3its.de>

On Tue, 15 Jan 2002 04:13:49 +0100
Klaus Meyer <k.meyer@m3its.de> wrote:

> i've got serious problems using 2.4.x kernels using highmem support.
> It seems to me that i'm not the only one, but the difference to most
> other ones is,
> that i can't use highmem because the system performance is terrible
> slow.
> 
> the testbed:
> 1) Asus CUR-DLS (Server Set LE III) with two 1Ghz Pentiums, 2GB of ram

Interestingly I have about the same setup and use, only I transfer about 25 GB
a day via nfs to an Asus CUV4XD with 2 GB under 2.4.18-pre3 and do not
experience any problem so far. I haven't had any with 2.4.17, too. Cache is
pretty heavy used, but I experience no slowdown or other weird things. Can this
be somehow chipset related? Maybe something about the DGE cards? I am using TP
100MBit tulip-based.

Regards,
Stephan



  reply	other threads:[~2002-01-15 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15  3:13 highmem=system killer, 2.2.17=performance killer ? Klaus Meyer
2002-01-15 15:00 ` Stephan von Krawczynski [this message]
2002-01-15 16:42   ` Klaus Meyer
2002-01-15 16:49     ` Stephan von Krawczynski
2002-01-18  2:04       ` Klaus Meyer
2002-01-18  4:56         ` Bill Davidsen
2002-01-18 14:34           ` Klaus Meyer
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 14:46 rwhron

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=20020115160018.18793569.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=k.meyer@m3its.de \
    --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.