From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kok, Auke" Subject: Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28 Date: Mon, 11 Aug 2008 11:50:57 -0700 Message-ID: <48A08A11.8040507@intel.com> References: <48A086B6.2000901@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, lkml To: Christoph Lameter Return-path: Received: from mga14.intel.com ([143.182.124.37]:17388 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752093AbYHKSxU (ORCPT ); Mon, 11 Aug 2008 14:53:20 -0400 In-Reply-To: <48A086B6.2000901@linux-foundation.org> Sender: netdev-owner@vger.kernel.org List-ID: Christoph Lameter wrote: > It seems that the network stack becomes slower over time? Here is a list of > tbench results with various kernel versions: > > 2.6.22 3207.77 mb/sec > 2.6.24 3185.66 > 2.6.25 2848.83 > 2.6.26 2706.09 > 2.6.27(rc2) 2571.03 > > And linux-next is: > > 2.6.28(l-next) 2568.74 > > It shows that there is still have work to be done on linux-next. Too close to > upstream in performance. > > Note the KT event between 2.6.24 and 2.6.25. Why is that? is this with SLAB or with SLUB? SLUB has been known to impact network performance... Auke