Messages in this thread | | | Date | Tue, 30 Nov 1999 08:31:46 +0000 (GMT) | From | Tigran Aivazian <> | Subject | Re: 2.3.29: ramdisk still broken. |
| |
does initrd not work with BDE's fix?
Bruce Elliot's fix is on my page:
http://www.ocston.org/~tigran/patches/other/bde-ramdisk-2.3.29-p1.patch
Regards, ------ Tigran A. Aivazian | http://www.sco.com Escalations Research Group | tel: +44-(0)1923-813796 Santa Cruz Operation Ltd | http://www.ocston.org/~tigran
On Fri, 26 Nov 1999, Khimenko Victor wrote:
> In <Pine.Linu.4.10.9911251630490.389-100000@mikeg.weiden.de> Mike Galbraith (mikeg@weiden.de) wrote: > > On Thu, 25 Nov 1999, Tigran Aivazian wrote: > > >> On Thu, 25 Nov 1999, Mike Galbraith wrote: > >> > The way I see it, the ramdisk used to work by making it's data persistent > >> > in the buffer cache. Today, data doesn't live in the buffer cache, it > >> > lives in the page cache. Ergo, the task at hand is to figure out how > >> > to make data in the page cache persistent rather than copying that data > >> > back and forth. > >> > >> Another view of the situation may be - ramdisk used to be static but then > >> started to rely on buffer cache. Now it can no longer rely on buffer > >> cache. Therefore, shouldn't it go back to being static? > > > I did that before trying anything else.. took it out of buffer cache > > all together and used vmalloc instead. Made for a pretty slow ramdisk. > > Can you send me that version ? For initrd speed is not an issue: it'll just > need to work somehow. Slow is Ok for initrd... > > > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |