On Thu, 14 Apr 2011, Eric Dumazet wrote: > Not sure its a win for my servers, where CONFIG_PREEMPT_NONE=y Well the fast path would then also be irq safe. Does that bring us anything? We could not do the cmpxchg in the !PREEMPT case and instead simply store the value. The preempt on/off seems to be a bigger deal for realtime. > Maybe use here latest cmpxchg16b stuff instead and get rid of spinlock ? Shaohua already got an atomic in there. You mean get rid of his preempt disable/enable in the slow path? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>