> Below is a patch that demonstrates standard messages for ethernet device
> drivers. I would like your feedback on the concept of standard network
> messages, and any suggestions for messages to include.
Very useful! I'd like to see a short note on this in Documentation/
networking..Or perhaps if there is already a RAS best practices
kind of doc or something, add to that? (sorry, havent checked)
But it would be handy for people who wanted to contribute
patches for other drivers.
Essentially, things like some guidelines on classifying some
of those messages, when creating new messages. eg when is
something a state change and when is it a performance event?
I notice some slight ambiguity in your defs..(sorry, very
minor nitpick :)).
I'd certainly like to see messages from the driver when the
card enters/leaves promiscuous mode, as an example of things
we'd like to add...
thanks,
Nivedita
> The intent of the standard message change is to:
> 1) Ensure key events are communicated to user space in a predictable
> way, enabling automated diagnostic systems or error log analysis,
> 2) Reduce the number of puzzling messages that are logged -- in this
> case, by replacing them with standard messages, and/or
> 3) Identify the device (or driver name) that is responsible for the error.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/