From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: raz@mailhost.directlink.net
Cc: linux-mm@kvack.org
Subject: Re: >4GB memory support.. ?
Date: Tue, 2 Nov 1999 15:10:29 -0800 (PST) [thread overview]
Message-ID: <199911022310.PAA73648@google.engr.sgi.com> (raw)
In-Reply-To: <199911021653859.SM00207@mailhost.directlink.net> from "Javan Dempsey" at Nov 2, 99 04:53:21 pm
>
> Anyone have any plans of tackling >4GB support? We just rolled some machines into production with 4GB recently, and are looking at needing support for more mem if remotely possible soon. Our machines will currently take upto 6GB. Kanoj? =)
>
Ingo Molnar from RedHat has put in the 64Gb support code into 2.3.
You can turn on this support during make config by
Processor type and features -> High Memory Support.
Kanoj
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-11-02 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 22:53 Javan Dempsey
1999-11-02 23:10 ` Kanoj Sarcar [this message]
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=199911022310.PAA73648@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=raz@mailhost.directlink.net \
/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