From: Joel Jaeggli <joelja@uoregon.edu>
To: "gmu 2k6" <gmu2006@gmail.com>
Cc: davids@webmaster.com, "Thomas Stewart" <thomas@stewarts.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Only 3.2G ram out of 4G seen in an i386 box
Date: Wed, 9 Aug 2006 07:48:15 -0700 [thread overview]
Message-ID: <20060809074815.bec7f32c.joelja@uoregon.edu> (raw)
In-Reply-To: <f96157c40608082351j301efa57n412284f8d28124ef@mail.gmail.com>
On Wed, 9 Aug 2006 08:51:41 +0200
"gmu 2k6" <gmu2006@gmail.com> wrote:
> > Are these technical notes supposed to be so funny?
> >
> > DS
>
> I guess this is all related to older Intel chipsets, right? I mean the
> chipset *75X something I'm going to have in the new box I will get
> soonish will support up to 8 GiB. I hope it does not mean that it will
> be capped at 7.4GiB although I will only have 4GiB installed for now.
most modern 64 bit x86 systems will relocate this memory hole to somewhere else within the address space (memory hoisting)... You'll probably find the it reappers the first time you buy a system with 1TB of ram...
> -
> 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/
next prev parent reply other threads:[~2006-08-09 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 8:24 Thomas Stewart
2006-08-08 10:15 ` Paul P Komkoff Jr
2006-08-08 19:51 ` David Schwartz
2006-08-09 6:51 ` gmu 2k6
2006-08-09 14:48 ` Joel Jaeggli [this message]
2006-08-09 14:54 ` gmu 2k6
2006-08-10 21:09 ` Simen Thoresen
2006-08-11 11:08 ` gmu 2k6
2006-08-13 10:54 ` Simen Thoresen
2006-08-10 13:04 ` Thomas Stewart
2006-08-08 9:13 Mikael Pettersson
2006-08-08 10:01 ` Thomas Stewart
[not found] <fa.FhtZk3YiH9OyGCt4iXIGt+vYtos@ifi.uio.no>
2006-08-08 14:22 ` Robert Hancock
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=20060809074815.bec7f32c.joelja@uoregon.edu \
--to=joelja@uoregon.edu \
--cc=davids@webmaster.com \
--cc=gmu2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@stewarts.org.uk \
/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
all inboxes | Powered by JetHome®