On Thu, Jun 24, 2010 at 01:02:50PM +1000, npiggin@xxxxxxx wrote: > RCU free the struct inode. This will allow: Rather than what it will allow, what are the constraints this imposes on allocating and freeing a struct inode? e.g. XFS embeds the struct inode in a larger inode structure and does it's own allocation, caching and freeing of the larger structure outside of the VFS functionality. Does this need to be converted to RCU? Do we need to do more initialisation of the struct inode than we currently do? What functions/call chains now implicitly require RCU freeing semantics on the struct inode for safe operation? What else do we need to be aware of? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
