On 03/31/2015 06:17 PM, Dan Williams wrote:
> On Tue, Mar 31, 2015 at 6:27 AM, Boaz Harrosh <boaz@xxxxxxxxxxxxx> wrote:
>>
>> Some error checks had unlikely some did not. Put unlikely
>> on all error handling paths.
>> (I like unlikely for error paths specially for readability)
>
> "unlikely()" is not a readability hint, it's specifically for branches
> that profiling shows adding it makes a difference. Just delete them
> all until profiling show they make a difference. They certainly don't
> make a difference in the slow paths.
>
Why?
So we do not fill up the branch predictor with useless predictions
that will never matter. What is so bad with that. It may be cold path
but added up all over it will show eventually.
I do not see what is the harm of telling the compiler.
"never store any prediction for this branch"
So since it can never (ever) harm any one or anything, and at the mass
if everywhere it was done this way it could actually help, then sure
it can be a readability thing. Since no harm done, right?
I still like it
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
