All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Low <lostlogic@gentoo.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: About highmem in 2.6
Date: Thu, 12 Feb 2004 10:07:46 -0600	[thread overview]
Message-ID: <20040212160746.GB7002@lostlogicx.com> (raw)
In-Reply-To: <m3isidkkr6.fsf@defiant.pm.waw.pl>

On Thu, 02/12/04 at 05:02:53 +0100, Krzysztof Halasa wrote:
> Bongani Hlope <bonganilinux@mweb.co.za> writes:
> 
> > There is nothing wrong with that patch, the problem with Highmem support
> > on x86 is that is uses an Intel hack to address the full 1Gb of memory,
> > which make memory access a bit slower. The question is, does the 128Mb
> > additional memory worth that penalty?
> 
> 2GB/2GB split doesn't use any Intel hack nor highmem. In fact for
> 1 GB of RAM I use a little different split which covers the whole RAM
> and gives more virtual RAM, something like 1.2/2.8 GB.

Any chance of me getting a copy of the patch which allows the finer
grained tuning of the kernel/user split?

Thanks.

Brandon Low
> -- 
> Krzysztof Halasa, B*FH
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-02-12 16:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1o6EZ-2zO-27@gated-at.bofh.it>
     [not found] ` <1o7AZ-3PD-9@gated-at.bofh.it>
2004-02-11 19:13   ` About highmem in 2.6 Mark de Vries
2004-02-11 19:28     ` Bongani Hlope
2004-02-12  4:02       ` Krzysztof Halasa
2004-02-12 16:07         ` Brandon Low [this message]
     [not found]         ` <Pine.LNX.4.58.0402120945340.1009@fgevxr.nfculk.yna>
2004-02-14  1:54           ` Krzysztof Halasa
2004-02-12  6:48     ` Martin J. Bligh
2004-02-11 17:47 Luis Miguel García
2004-02-11 18:44 ` Dave McCracken

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=20040212160746.GB7002@lostlogicx.com \
    --to=lostlogic@gentoo.org \
    --cc=khc@pm.waw.pl \
    --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.