> In typical deployments outside of testing environment, this function is > called 5 times every system boot and never again. Does this information mean that a bit more fine-tuning is insignificant at such a source code place? >> Did the assignment for the local variable "rc" with a well-known error code >> influence the run-time characteristics in unwanted ways? >> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/staging/lustre/lustre/obdclass/genops.c?id=6a5b99a46bedc2cfbba96dec6d255c4b90af9ff8#n140 > > I am not sure what do you mean here. I suggest to take another look at corresponding implementation details. An error code is assigned to the variable "rc" before four memory allocations succeeded so far. We hope that this function will usually return zero as a constant for the indication of a successful execution. I find that this variable should not be touched in the preferred case. Will such an unnecessary assignment reduce the execution speed a bit for the desired file system initialisation? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
