public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Antonio Vargas <windenntw@gmail.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Bastiaan Naber <naber@inl.nl>, linux-kernel@vger.kernel.org
Subject: Re: a 15 GB file on tmpfs
Date: Wed, 20 Jul 2005 15:31:36 +0200	[thread overview]
Message-ID: <69304d110507200631564a73b1@mail.gmail.com> (raw)
In-Reply-To: <20050720132006.GI7050@harddisk-recovery.com>

On 7/20/05, Erik Mouw <erik@harddisk-recovery.com> wrote:
> On Wed, Jul 20, 2005 at 02:16:36PM +0200, Bastiaan Naber wrote:
> > I have a 15 GB file which I want to place in memory via tmpfs. I want to do
> > this because I need to have this data accessible with a very low seek time.
> 
> That should be no problem on a 64 bit architecture.
> 
> > I want to know if this is possible before spending 10,000 euros on a machine
> > that has 16 GB of memory.
> 
> If you want to spend that amount of money on memory anyway, the extra
> cost for an AMD64 machine isn't that large.
> 
> > The machine we plan to buy is a HP Proliant Xeon machine and I want to run a
> > 32 bit linux kernel on it (the xeon we want doesn't have the 64-bit stuff
> > yet)
> 
> AFAIK you can't use a 15 GB tmpfs on i386 because large memory support
> is basically a hack to support multiple 4GB memory spaces (some VM guru
> correct me if I'm wrong). Just get an Athlon64 machine and run a 64 bit
> kernel on it. If compatibility is a problem, you can still run a 32 bit
> i386 userland on an x86_64 kernel.
> 
> 
> Erik
> 
> --
> +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
> | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
> -

Bastian, Erik is dead-on on that one: go 64bit and forget all worries
about your 15GB filesize. Just don't forget to look not only x86-64
(intel or amd) but also itanium, ppc64 and s390 machines, you never
know about surprises!

-- 
Greetz, Antonio Vargas aka winden of network

http://wind.codepixel.com/

Las cosas no son lo que parecen, excepto cuando parecen lo que si son.

  reply	other threads:[~2005-07-20 13:31 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 [this message]
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
  -- 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=69304d110507200631564a73b1@mail.gmail.com \
    --to=windenntw@gmail.com \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naber@inl.nl \
    /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