Messages in this thread | | | Date | Wed, 27 Jan 1999 15:27:05 GMT | From | "Stephen C. Tweedie" <> | Subject | Re: RAMDISK Bug - 2.0.36 kernel (again) |
| |
Hi,
On Tue, 26 Jan 1999 17:23:27 +0000 (GMT), Bill Melotti <billy@cognito.co.uk> said:
> It is as if the RAMDISK code as not marked the buffers it uses as > unavailable for app code. I looked through the code and see it sets the > BH_Protected flag in the file buffer structs. However I also see that > there are 2 or 3 places (fs/buffers.c and somewhere in ext2 hierarchy) > where these can be cleared.
Ramdisk does reserve its buffers, at least until you start deleting files on the ramdisk (which is the only place we would clear the protected flag).
> Can anyone offer any help/comments/suggestions ?
Adding swap is the only recommended the way to avoid painful VM deaths like this, I'm afraid. Otherwise, just make the ramdisk as small as possible: using mke2fs options to reduce the number of inodes on the ramdisk, or even using the minix fs, might help.
--Stephen
- 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/
| |