From: Robert Hancock <hancockr@shaw.ca>
To: michal.k.k.piotrowski@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20-rc6 ramdisk problem
Date: Wed, 31 Jan 2007 17:54:38 -0600 [thread overview]
Message-ID: <45C12C3E.6010902@shaw.ca> (raw)
In-Reply-To: <fa.nr9vhGrVS5zmSNQEe1vQ/Ktii9w@ifi.uio.no>
Michal Piotrowski wrote:
> Hi,
>
> I want to create a large ramdisk - 1GB
>
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=1
> CONFIG_BLK_DEV_RAM_SIZE=4096
> CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
>
> kernel comman line: ramdisk_size=1000000
>
..
>
> With ramdisk_size=500000 everything is ok.
>
> machine
> CPU P4 (ia32)
> 2 GB RAM
>
> Is this is a hardware (arch) or software limitation? Maybe a bug?
>
> Regards,
> Michal
I'm not sure if there's an inherent max ramdisk size limit, however I
should point out that in most cases, using a tmpfs or ramfs file system
is better than old-style ramdisks. Those filesystems return unused
memory to the kernel (ramdisks statically allocate the entire space) and
also avoid the filesystem overhead of ramdisks (the files are mapped
into pagecache directly).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-01-31 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.nr9vhGrVS5zmSNQEe1vQ/Ktii9w@ifi.uio.no>
2007-01-31 23:54 ` Robert Hancock [this message]
2007-02-01 0:06 ` 2.6.20-rc6 ramdisk problem Thomas Gleixner
2007-02-01 0:14 ` Robert Hancock
2007-02-01 0:40 ` Thomas Gleixner
2007-01-31 13:55 Michal Piotrowski
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=45C12C3E.6010902@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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.