linux-kernel - Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 27 Jan 2009 13:15:45 -0800
From:	Jonathan Campbell <jon@...dgrounds.com>
To:	Mark Knecht <markknecht@...il.com>
CC:	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices


> If I was to build this and try it our (not saying I have time right
> now though) then as root how do I determine what size file system I
> can build? Do I run fdisk against /dev/fb0 and look at what portion is
> unallocated?
>
>   
The capacity is automatically set to the amount of VRAM out there, based 
on what the PCI subsystem says the resource length is. So if you mount 
your ATI Radeon's VRAM and it has 512MB on it, you'll get a filesystem 
with a capacity of 512MB.

Fdisk is not necessary, the filesystem structures are maintained in 
system memory not VRAM. Like tmpfs/shmemfs the filesystem structures are 
discarded on unmount, though the contents are not cleared from VRAM.

Adding a mount parameter to override the PCI system reported length 
wouldn't be hard either.


--
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/