From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>,
Russell Coker <russell@coker.com.au>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: slightly [OT] highmem (was Re: 2.4.20 at kernel.org and data logging)
Date: Fri, 24 Jan 2003 20:03:38 +0300 [thread overview]
Message-ID: <20030124200338.A4338@namesys.com> (raw)
In-Reply-To: <200301241800.19072.Dieter.Nuetzel@hamburg.de>
Hello!
On Fri, Jan 24, 2003 at 06:00:19PM +0100, Dieter N?tzel wrote:
> > > higmem4GB / highmem64GB with "pae" or does it produce more overhead that
> > > you mention below?
> > You get no advantage of course.
> > But lots of overhead. Rumours have it that 256M systems with highmem
> > enabled kernels (default for RedHat beta it seems) are swapping much more
> > then when the same kernel is built with highmem off.
> But that could be because they have forgotten to enabled HIGHMEM IO?
> See Andrea Ancangeli's -aa kernels.
What HIGHMEM IO? There is exactly NO highmem, so sighmem IO code won't be used.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-24 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 23:51 2.4.20 at kernel.org and data logging Sewell, Cassandra D (Cassandra)
2003-01-17 0:33 ` Manuel Krause
2003-01-18 10:25 ` Russell Coker
2003-01-18 15:57 ` Chris Mason
2003-01-19 10:45 ` Russell Coker
2003-01-23 23:10 ` slightly [OT] highmem (was Re: 2.4.20 at kernel.org and data logging) Manuel Krause
2003-01-23 23:40 ` Russell Coker
2003-01-24 0:18 ` Manuel Krause
2003-01-24 0:24 ` Russell Coker
2003-01-24 7:50 ` Oleg Drokin
2003-01-24 17:00 ` Dieter Nützel
2003-01-24 17:03 ` Oleg Drokin [this message]
2003-01-24 17:15 ` Dieter Nützel
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=20030124200338.A4338@namesys.com \
--to=green@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=manuel.krause@mb.tu-ilmenau.de \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.