On Mon, 2012-03-19 at 14:31 -0400, Ted Ts'o wrote: > On Mon, Mar 19, 2012 at 02:14:02PM -0400, David Miller wrote: > I've *already* gone far beyond the pr_fmt standardization, with the > ext4_msg() and ext4_error() system Please note the defects that were recently corrected there which occurred because of a lack of standardization both in prefix and termination style. > One of the other reasons why I don't like the pr_* system because it > doesn't go far enough for the pain that's involved with making such a > change pervasively across the entire kernel. Any logging system, with or without an external notification mechanism, will be painful. pr_<foo> is at least a small start. I'd like to see a notification mechanism, perhaps ala netlink/ethtool to extend pr_<foo> or another call. A lot of these printk/pr_<level> uses really could generate notifications. > What I'd really like to > see is a system that allows for semi-structured logging --- where > structured data such as the block device involved, whether it's at a > device driver driver, block layer, cfq or proportional I/O layer, or > file system layer, was consistently named, and squirted out a high > efficiency interface such as netlink or an ftrace ring buffer. Yay, we agree. cheers, Joe -- 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
