inode->i_dirty_buffers redundant ?
now that we have inode->i_mapping->dirty_pages, what do we need inode->i_dirty_buffers for ? I understand the latter was added for the O_SYNC changes before dirty_pages came into the picture. but now both seem to be doing more or less the same thing.
ganesh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · V Ganesh
now that we have
inode->i_mapping->dirty_pages, what do we needinode->i_dirty_buffersfor ? I understand the latter was added for theO_SYNCchanges beforedirty_pagescame into the picture. but now both seem to be doing more or less the same thing.
inode->i_mapping->dirty_pages contains only mapped data pages of the inode, not metadata.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Hi,
Quoted 2 lines · V Ganesh
now that we have
inode->i_mapping->dirty_pages, what do we needinode->i_dirty_buffersfor ?
Metadata. Specifically, directory contents and indirection blocks.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/