Can you rerun this test with random source/destination addresses, to get more realistic (for some configurations) numbers? He can do this, but the issues we're trying to tackle first have nothing to
Can you rerun this test with random source/destination addresses, to get more realistic (for some configurations) numbers? He can do this, but the issues we're trying to tackle first have nothing to
[sorry, wrong Cc: the first time] net/core/skbuf.c has a small per-cpu pool to keep some hot skbufs around instead of returning them to the system allocator. But if you loook at the slab allocator we
The code was added before slab grew an own per cpu allocator. AFAIK it wasn't removed because the "extreme routing" people like Jamal and Robert O. still saw small advantages, but it's probably worth
Hello! Well just happened test without it yesterday... Manfred is working on some improvements of the slab (magazine layer) so I tested this. It seems to do improve performance. I also removed the sk
Do we need a test run without Manfreds (soon coming) magazine patch too? Nope. I'm personally convinced, someone send me a patch to kill it off and I'll apply it.
Robert's first reply on this subject had it attached.. I deleted it, can someone resend me a copy? When I ask for a patch, it usually means that I've /dev/null'd the entire thread already.