On Tue, 2012-03-20 at 13:24 +1100, Indan Zupancic wrote: > If it does then perhaps the fast path should be made faster by inlining > the code instead of calling a function which may not be cached. > inlining 400 times a sequence of code is waste of icache, you probably missed this. I spent a lot of time on working on this implementation, tried many different strategies before choosing the one in place. Listen, I am tired of this thread, it seems you want to push changes that have almost no value but still need lot of review. Unless you make benchmarks and can make at least 5 % improvement of the speed, or improve maintainability of this code, I am not interested. We certainly _can_ one day have sizeof(struct sk_buff) > 256, and actual code is ready for this. You want to break this for absolutely no valid reason. We _can_ change fields order anytime in struct sk_buff, even if you state "its very unlikely that those fields are ever moved to the end of sk_buff". -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
