Messages in this thread | | | Date | Thu, 29 Apr 2004 09:27:30 +0100 | From | Christoph Hellwig <> | Subject | Re: 2.6.6-rc{1,2} bad VM/NFS interaction in case of dirty page writeback |
| |
On Thu, Apr 29, 2004 at 11:48:21AM +1000, Nathan Scott wrote: > Another thing I think XFS could make good use of on the generic > buffered IO path would be mpage_readpages and mpage_writepages > variants that can use a get_blocks_t (like the direct IO path) > instead of the single-block-at-a-time get_block_t interface thats > used now. The existence of such beasts would probably impact the > direction xfs_aops.c takes a fair bit I'd guess Christoph?
For mpage_readpages - yes. To use mpage_writepages from XFS I'd need a large-scale rewrite to handle delayed allocations and unwritten extents, so at least for the 2.6.x timeframe we're probably better of keeping our own ->writepages inside XFS.
- 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/
| |