Matthew Wilcox wrote:
Rearrange a lot of the functions in the file to get rid of all the forward
declarations.
What thoughts, if any, have been given to post-patch code arrangement,
besides eliminating prototypes?
This always struck me as a counterproductive exercise when taken by
itself. Sure, prototypes were eliminated, but was code packed together
in an efficient way afterwards? Ideally hot path code should be close
together, ditto for various other things like error handling code.
Without further explanation or details about your post-patch analysis,
how do we even know the new code arrangement doesn't negatively impact
i-cache overall?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
