From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 1-2-3 GB
Date: 13 Jan 2002 12:24:03 -0800 [thread overview]
Message-ID: <a1sqd3$nc6$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020112125625.E1482@inspiron.school.suse.de> <Pine.LNX.4.21.0201121825200.1105-100000@localhost.localdomain>
Followup to: <Pine.LNX.4.21.0201121825200.1105-100000@localhost.localdomain>
By author: Hugh Dickins <hugh@veritas.com>
In newsgroup: linux.dev.kernel
>
> Usually not a problem: but if you configure for 1GB of user virtual
> and 3GB of kernel virtual, and you have more than 1GB of physical
> memory (as you normally would if chose HIGHMEM64G), then there's
> a page at physical address 0x3ffff000, directly mapped to virtual
> address 0x7ffff000. And if that page happens to get used for the
> pmd of a process, then on exit the free_one_pgd loop wraps over
> to carry on freeing "entries" at 0x80000000, 0x80000008, ...
> A lot of pmd_ERROR messages, but eventually an entry scrapes
> through the pmd_bad test and is wrongly freed, not so good.
>
By the way, expect user programs to fail due to lack of address space
if you only give them 1 GB of userspace. At 1 GB of userspace there
is *no* address space which is compatible with the normal address
space map available to the user process.
I would personally vote against including that particular option.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-13 20:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 5:45 [PATCH] 1-2-3 GB rwhron
2002-01-12 7:32 ` H. Peter Anvin
2002-01-12 13:17 ` Andrea Arcangeli
2002-01-12 17:26 ` Albert D. Cahalan
2002-01-12 17:42 ` Andrea Arcangeli
2002-01-12 18:28 ` Albert D. Cahalan
2002-01-12 19:07 ` BIO Usage Error or Conflicting Designs Andre Hedrick
2002-01-12 20:05 ` Jens Axboe
2002-01-13 1:15 ` Andre Hedrick
2002-01-13 12:59 ` Jens Axboe
2002-01-13 19:59 ` Andre Hedrick
2002-01-14 6:42 ` Jens Axboe
2002-01-12 20:59 ` [PATCH] 1-2-3 GB H. Peter Anvin
2002-01-12 11:56 ` Andrea Arcangeli
2002-01-12 15:50 ` rwhron
2002-01-12 19:22 ` Hugh Dickins
2002-01-12 21:02 ` Andrew Morton
2002-01-13 20:24 ` H. Peter Anvin [this message]
2002-01-13 23:11 ` Marvin Justice
2002-01-14 0:03 ` H. Peter Anvin
2002-01-14 0:46 ` Alan Cox
2002-01-14 2:21 ` Rik van Riel
2002-01-18 21:18 ` Pavel Machek
2002-01-19 0:24 ` Hugh Dickins
2002-01-12 21:41 ` rwhron
2002-01-12 22:34 ` rwhron
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 14:07 rwhron
2002-01-15 17:48 ` Dave Jones
2002-01-16 2:12 ` H. Peter Anvin
2002-01-23 3:53 ` 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='a1sqd3$nc6$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox