[EMAIL PROTECTED] said: > Also, if you care about memory usage, you're likely to be much better > off using ramfs rather than something like "ext2 on ramdisk". You > won't get the double buffering. That'll be even more useful once we can completely configure out all support for block devices too. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Patch (repost): cramfs memory ... Alan Cox
- Re: Patch (repost): cramfs memory ... Eric W. Biederman
- Re: Patch (repost): cramfs memory corru... Christoph Rohland
- Re: Patch (repost): cramfs memory ... Christoph Hellwig
- Re: Patch (repost): cramfs mem... Christoph Rohland
- Re: Patch (repost): cramfs memory ... Alan Cox
- Re: Patch (repost): cramfs mem... Christoph Rohland
- Re: Patch (repost): cramfs memory corruptio... David L. Parsley
- Re: Patch (repost): cramfs memory corru... Linus Torvalds
- Re: Patch (repost): cramfs memory corruption fix Linus Torvalds
- Re: Patch (repost): cramfs memory corruption fix David Woodhouse
- Re: Patch (repost): cramfs memory corruption fi... Shane Nay
- Re: Patch (repost): cramfs memory corruption fi... David Woodhouse
- [PATCH] one-liner fix for bforget() honoring BH_Pro... David L. Parsley
- Re: [PATCH] one-liner fix for bforget() honorin... Linus Torvalds