Well, frankly, the interface should be that the user code sends the
command it needs, and waits for it. With no policy in the kernel at all.
Now, for backwards compatibility reasons we cannot do that generically,
and some things (not format, though), may be common enough that the
"library code" to do the normal thing is in the kernel. But on the whole,
the question should not be "how long should the timeout be", but more
along the lines of "how can we make this easy to interface to existing and
new applications _without_ having policy decisions like timeouts and
number of retries".
Linus
-
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/