[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0810311300130.7072@wrl-59.cs.helsinki.fi>
Date: Fri, 31 Oct 2008 13:01:45 +0200 (EET)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: Eric Dumazet <dada1@...mosbay.com>
cc: David Miller <davem@...emloft.net>, shemminger@...tta.com,
zbr@...emap.net, rjw@...k.pl, mingo@...e.hu,
s0mbre@...rvice.net.ru, a.p.zijlstra@...llo.nl,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>, efault@....de,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [tbench regression fixes]: digging out smelly deadmen.
On Fri, 31 Oct 2008, Eric Dumazet wrote:
> David Miller a écrit :
> > From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
> > Date: Fri, 31 Oct 2008 11:40:16 +0200 (EET)
> >
> > > Let me remind that it is just a single process, so no ping-pong & other
> > > lock related cache effects should play any significant role here, no? (I'm
> > > no expert though :-)).
> >
> > Not locks or ping-pongs perhaps, I guess. So it just sends and
> > receives over a socket, implementing both ends of the communication
> > in the same process?
> >
> > If hash chain conflicts do happen for those 2 sockets, just traversing
> > the chain 2 entries deep could show up.
>
> tbench is very sensible to cache line ping-pongs (on SMP machines of course)
...Sorry to disappoint you but we were discussion there on my AIM9
tcp_test results :-).
--
i.
Powered by blists - more mailing lists