On 10/9/18 2:24 PM, Heiner Kallweit wrote: > Reordering the struct members to fill the holes could be a little tricky > and could have side effects because it may make a performance difference > whether certain members are in one cacheline or not. > And whether it's worth to spend this effort (incl. the related risks) > just to save a few bytes (also considering that typically we have quite > few instances of struct net_device)? >
It would be good to get net_device below 2048 without affecting performance. Anything else is just moving elements around for the same end allocation (rounds up to 4096).
