Messages in this thread | | | Date | Wed, 12 May 2004 07:33:29 -0600 | From | marcus hall <> | Subject | Re: Block device swamping disk cache |
| |
On Tue, May 11, 2004 at 05:26:43PM -0700, Andrew Morton wrote: > no, sorry, it'll still happen. I haven't fixed the ramdisk driver yet. > > The problem is that ->memory_backed means both "doesn't contribute > to dirty memory" and also "doesn't need writeback". > > These concepts need to be split apart for the ramdisk driver. I'll do it > for 2.6.7, promise.
Well, I believe that the inodes that are marked as memory_backed are for the ramdisk, and that isn't really a problem. The block device that I am writing to is a compact flash, so it's going through the ide-disk device. I do not see this inode show up on any superblock's dirty queue (since it doesn't appear that mark_inode_dirty() is being called for it). So the question I am asking is, what strategy is *supposed* to be in place to flush the blocks out? (Or is this a hole that isn't plugged?)
Marcus Hall marcus@tuells.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |