On Sun, Aug 09, 2009 at 10:42:17PM -0500, Eric Sandeen wrote: > Theodore Ts'o wrote: > > Allow mballoc debugging to be enabled at run-time instead of just at > > compile time. > > > > Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx> > > --- > > fs/ext4/Kconfig | 9 ++++++ > > fs/ext4/mballoc.c | 81 ++++++++++++++++++++++++++++++++++++++-------------- > > fs/ext4/mballoc.h | 16 ++++++++-- > > 3 files changed, 80 insertions(+), 26 deletions(-) > > This looks fine to me, though is there any reason to add the debug > verbosity level at this point, when it's all just "1?" What I'm thinking about doing is to use a bitmask instead of a verbosity level. That way it will be possible to selectively enable some debugging print messages and not others. In the long run the right answer is to use ftrace instead, but this is faster and more convenient when doing surgery/development on the mballoc code. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
