I want to change inode->i_flags access to be atomic -- there are some locking oddities right now, I think, and I want to use a new inode flag to signal mtime updates from page_mkwrite. The problem is that i_flags is an unsigned int, and making it an unsigned long seems like a waste, but there aren't any u32 atomic bitops. What should I do? Suck it up and waste four bytes on 64-bit machines? In general, having atomic flag words be long seems likely to waste bits on 64-bit architectures. --Andy -- 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
