Re: Network latency regressions from 2.6.22 to 2.6.29

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Christoph Lameter
Date: Friday, April 17, 2009 - 6:46 am

On Thu, 16 Apr 2009, David Miller wrote:


Only the kernel version was changed on both systems. Changing only a
single system would have meant considering complex interactions between
the network layers of varying versions which would make
the problem even more difficult to track down.

I changed one thing: The kernel version.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 9:10 am)
Re: Network latency regressions from 2.6.22 to 2.6.29, Rick Jones, (Thu Apr 16, 10:21 am)
Re: Network latency regressions from 2.6.22 to 2.6.29, Ben Hutchings, (Thu Apr 16, 11:07 am)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 12:02 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 12:06 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Eric Dumazet, (Thu Apr 16, 12:29 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 12:33 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Eric Dumazet, (Thu Apr 16, 12:43 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Eric Dumazet, (Thu Apr 16, 12:50 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 12:55 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Thu Apr 16, 1:01 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Ben Hutchings, (Thu Apr 16, 2:19 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Michael Chan, (Thu Apr 16, 2:57 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, David Miller, (Thu Apr 16, 3:47 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, David Miller, (Thu Apr 16, 3:47 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, David Miller, (Thu Apr 16, 3:59 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, David Miller, (Thu Apr 16, 4:00 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Fri Apr 17, 6:46 am)
Re: Network latency regressions from 2.6.22 to 2.6.29, Christoph Lameter, (Fri Apr 17, 6:47 am)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Fri Apr 17, 9:42 am)
Re: Network latency regressions from 2.6.22 to 2.6.29, Ilpo Järvinen, (Fri Apr 17, 2:43 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Mon Apr 20, 10:29 am)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Mon Apr 20, 11:13 am)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Mon Apr 20, 12:16 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Evgeniy Polyakov, (Mon Apr 20, 12:44 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Mon Apr 20, 2:14 pm)
Re: Network latency regressions from 2.6.22 to 2.6.29 (res ..., Christoph Lameter, (Tue Apr 21, 7:00 am)
Re: Network latency regressions from 2.6.22 to 2.6.29 (MSI ..., Christoph Lameter, (Tue Apr 21, 12:36 pm)