Hi all, Currently debugging statements for the HFS+ driver are enabled/disabled at compiled time by modifying DBG_MASK towards the top of linux/fs/hfsplus/hfsplus_fs.h. Is there a strong reason against converting that to use the dynamic debug feature (linux/Documentation/dynamic-debug-howto.txt) instead? I assume there is a performance penalty for dynamic debugging vs compile-time config, and file system is probably one area where performance is important. So the other question is, does anybody know what sort of performance penality it makes? One small reason I am thinking of converting is every time one adds a feature (like Vyacheslav's recent xttr patch series), one adds a bit mask. That obviously colides with outside-kernel patches like the journalling ones, since everybody uses the next-available bit. Other than dynamic-debugging, is there a better way of handling the debugging statements in the hfsplus driver, than it is currently doing? Hin-Tak -- 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
