netdev
[Top] [All Lists]

Re: [RFC] TCP congestion schedulers

To: Rick Jones <rick.jones2@xxxxxx>
Subject: Re: [RFC] TCP congestion schedulers
From: Olaf Kirch <okir@xxxxxxx>
Date: Tue, 22 Mar 2005 02:41:54 +0100
Cc: netdev@xxxxxxxxxxx
In-reply-to: <423F627C.2060100@xxxxxx>
References: <20050225120814.5fa77b13@xxxxxxxxxxxxxxxxx> <20050309210442.3e9786a6.davem@xxxxxxxxxxxxx> <4230288F.1030202@xxxxxxxxx> <20050310182629.1eab09ec.davem@xxxxxxxxxxxxx> <20050311120054.4bbf675a@xxxxxxxxxxxxxxxxx> <20050311201011.360c00da.davem@xxxxxxxxxxxxx> <20050314151726.532af90d@xxxxxxxxxxxxxxxxx> <m13bur5qyo.fsf@xxxxxx> <Pine.LNX.4.58.0503211605300.6729@xxxxxxxxxxxxxx> <423F627C.2060100@xxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Mon, Mar 21, 2005 at 04:10:36PM -0800, Rick Jones wrote:
> I would put-forth netperf - but then I'm of course biased.  It is 

I think that was one of the benchmarks where the ia64 slowdown with
LSM was diagnosed; netperf suffered some 10-15% degradation. And that was
just with the capability module loaded, no fancy stuff going on.
After we hacked up LSM to inline the capability checks in the default
case, performance was back to normal.

We didn't bother to pin-point where the loss actually occured, but my
suspicion is the major offender was the per-skb check.

Olaf
-- 
Olaf Kirch   |  --- o --- Nous sommes du soleil we love when we play
okir@xxxxxxx |    / | \   sol.dhoop.naytheet.ah kin.ir.samse.qurax

<Prev in Thread] Current Thread [Next in Thread>