From: Erik Mouw <erik@harddisk-recovery.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a 15 GB file on tmpfs
Date: Wed, 20 Jul 2005 16:44:21 +0200 [thread overview]
Message-ID: <20050720144421.GK7050@harddisk-recovery.com> (raw)
In-Reply-To: <dbljub$mgm$1@news.cistron.nl>
On Wed, Jul 20, 2005 at 01:35:07PM +0000, Miquel van Smoorenburg wrote:
> In article <20050720132006.GI7050@harddisk-recovery.com>,
> Erik Mouw <erik@harddisk-recovery.com> wrote:
> >On Wed, Jul 20, 2005 at 02:16:36PM +0200, Bastiaan Naber wrote:
> >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).
>
> I'm no VM guru but I have a 32 bit machine here with 8 GB of
> memory and 8 GB of swap:
>
> # mount -t tmpfs -o size=$((12*1024*1024*1024)) tmpfs /mnt
> # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 19228276 1200132 17051396 7% /
> tmpfs 12582912 0 12582912 0% /mnt
>
> There you go, a 12 GB tmpfs. I haven't tried to create a 12 GB
> file on it, though, since this is a production machine and it
> needs the memory ..
I stand corrected.
> So yes that appears to work just fine.
The question is if it's a good idea to use a 15GB tmpfs on a 32 bit
i386 class machine. I guess a real 64 bit machine will be much faster
in handling suchs amounts of data simply because you don't have to go
through the hurdles needed to address such memory on i386.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2005-07-20 14:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 12:16 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 [this message]
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
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=20050720144421.GK7050@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.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
all inboxes | Powered by JetHome®