linux-kernel - Re: 2.6.20-rc6 ramdisk problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-id: <45C12C3E.6010902@shaw.ca>
Date:	Wed, 31 Jan 2007 17:54:38 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	michal.k.k.piotrowski@...il.com
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.20-rc6 ramdisk problem

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@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/