On Mon, Jan 19, 2015 at 10:05 PM, Hagen Paul Pfeifer <hagen@xxxxxxxx> wrote: > On 19 January 2015 at 21:05, Hannes Frederic Sowa > <hannes@xxxxxxxxxxxxxxxxxxx> wrote: > >> Oh yes, although we never exposed an ip route knob for that, it is still >> possible users did set manually, so we cannot get rid of that, agreed. > > I thought about that, sure but come to the conclusion that the code > cleanup outweigh an potential user somewhere in space (well, the use > case is broken and should be fixed). Additionally, I left the > RTAX_FEATURE_ALLFRAG (as mentioned) and removed all related > functionality - no visible API change (except no-op behavior). > > Davem, I will sent the patch anyway. Feel free to accept/ignore. > > Hagen > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Hi. Last time I was inquiring about depracated atomic fragments, people were concerned that there wasn't enough practical data to decide whether to go forward or not. Would a sysctl with it turned on by default be a good option, until we are 100% sure ? Kind regards, //Logan C-x-C-c -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html