All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Bernd Eckenfels <be-mail2005@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a 15 GB file on tmpfs
Date: Fri, 22 Jul 2005 23:10:59 +0200	[thread overview]
Message-ID: <42E160E3.8010006@stesmi.com> (raw)
In-Reply-To: <20050722162539.GA25577@lina.inka.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bernd Eckenfels wrote:
> On Fri, Jul 22, 2005 at 01:00:18PM +0200, Stefan Smietanowski wrote:
> 
>>>You cant have 16GB of Memory with 32bit CPUs.
>>
>>PAE
>>CONFIG_HIGMEM64G
>>Supports a 36bit address space, which Xeons do support.
> 
> 
> Yes right, I was just not aware recent hardware (still) supports that. I
> mean even mit 2MB modules most of them are specified only to 8GB. I would
> consider buying such a system quite foolish. All of the HP servers with 12GB
> and more seem to support EM64T. Do you know vendors who ship non-EM64T
> servers with more than 16GB?

http://www.intel.com/products/processor/xeon/index.htm

Shows that the lowest speed Xeon with EM64T is 2.83GHz.

http://commerce.euro.dell.com/dellstore/config/frameset.asp?c=607&n=3410&b=62417&m=gbp&cs=ukbsdt1&sbc=ukbsdpedge&v=d&cu=etstore&l=en&s=ukbsd&store=ukbsd

Shows a system taking 1-4 of those processors at 2.0, 2.2, 2.7 and
3.0GHz, making them 32bit only.

Memory you can configure is from 1GiB (4x256MiB) to 32GiB (16x2GiB).

If I'd buy a server I wouldn't buy one of those however, I'm just
answering the question.

Disclaimer: I do not have anything to do with either of the above
mentioned vendors. I just looked up the first vendor that came into
my head.

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFC4WDjBrn2kJu9P78RAn9RAJ9wRffW5VB0WbRgRBNjfN9+k3XMvgCgtWAO
mu8p8nj8iIpNIkuYiMkiTuI=
=9kQz
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-22 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 12:16 a 15 GB file on tmpfs Bastiaan Naber
2005-07-20 13:20 ` Erik Mouw
2005-07-20 13:31   ` Antonio Vargas
2005-07-20 13:35   ` Miquel van Smoorenburg
2005-07-20 14:44     ` Erik Mouw
2005-07-20 15:23       ` Antonio Vargas
2005-07-21  2:13         ` Jim Nance
2005-07-20 15:18 ` Jan Engelhardt
2005-07-21  6:25 ` Denis Vlasenko
2005-07-21  8:42 ` Bernd Petrovitsch
2005-07-21  9:12   ` Stefan Smietanowski
2005-07-21  9:39     ` Bernd Petrovitsch
2005-07-22 10:36 ` Bernd Eckenfels
2005-07-22 11:00   ` Stefan Smietanowski
2005-07-22 16:25     ` Bernd Eckenfels
2005-07-22 21:10       ` Stefan Smietanowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-21 15:25 Andrew Burgess
2005-07-22  9:39 Cabaniols, Sebastien
2005-07-22 10:38 linux

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=42E160E3.8010006@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=be-mail2005@lina.inka.de \
    --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.