Messages in this thread | | | From | David Howells <> | Subject | Re: 2.6.10-mm1 | Date | Thu, 06 Jan 2005 13:04:04 +0000 |
| |
Christoph Hellwig <hch@infradead.org> wrote:
> > > add-page-becoming-writable-notification.patch > > > Add page becoming writable notification > > > > David, this still has the bogus address_space operation in addition to > > the vm_operation. page_mkwrite only fits into the vm_operations scheme, > > so please remove the address_space op. Also the code will be smaller > > and faster witout that indirection.. > > Here's the fix:
That's not right either. Filesystems really shouldn't be overloading the vm_ops on memory mappings (as has been made clear to me) and the VM low-level paging routines shouldn't be touching a_ops (as has also been made clear to me). I also have other reasons I don't want to have ordinary files with specialised vm_ops.
I suppose I could try and build a little knowledge about fscache into the VM... that might be reasonable.
Remember also that your change is going to affect NFS too eventually, assuming NFS caching support ends up being done this way. It may also affect other filesystems, such as SMB/CIFS and Coda eventually should they partake of fscache services too.
David - 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/
| |