On Fri, 30 Jun 2023, Chuck Lever wrote: > Here's something just for fun. I've converted nfsd4_encode_fattr4() > to use a bitmask loop, calling an encode helper for each attribute > to be encoded. Rotten tomatoes and gold stars are both acceptible. Tomatoes or stars .... it is a hard choice :-) I wonder what the compiler does with this code. If it unrolls the loop and inlines the functions - which it probably can do as the array of pointers is declared const - you end up with much the same result as the current code. And I wonder where the compiler puts the code in each conditional now. If it assumes an if() is unlikely, then it would all be out-of-line which sounds like part of your goal (or maybe just a nice-to-have). If the compiler does, or can be convinced to, do the unroll and inline and unlikely optimisations, then I think I'd give this a goal star. I guess in practice some of the attributes are "likely" and many are "unlikely". With the current code we could easily annotate that if we wanted to and thought (or measured) there was any value. With the looping code we cannot really annotate the likelihood of each. The code-generation idea is intriguing. Even if we didn't reach that goal, having the code highly structured as though it were auto-generated would be no bad thing. Thanks, NeilBrown
