[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <061d83fa-b1e6-651e-ccfe-c95544ae8bd2@users.sourceforge.net>
Date: Sat, 30 Jul 2016 08:24:46 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Oleg Drokin <oleg.drokin@...el.com>
Cc: devel@...verdev.osuosl.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>,
Bhumika Goyal <bhumirks@...il.com>,
lustre-devel@...ts.lustre.org
Subject: Re: [lustre-devel] staging: lustre: One function call less in
class_register_type() after error detection
> 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
Powered by blists - more mailing lists