Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751477AbYJaKmu (ORCPT ); Fri, 31 Oct 2008 06:42:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750741AbYJaKmj (ORCPT ); Fri, 31 Oct 2008 06:42:39 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:48046 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbYJaKmi (ORCPT ); Fri, 31 Oct 2008 06:42:38 -0400 Date: Fri, 31 Oct 2008 12:42:34 +0200 (EET) From: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" X-X-Sender: ijjarvin@wrl-59.cs.helsinki.fi To: David Miller cc: shemminger@vyatta.com, zbr@ioremap.net, rjw@sisk.pl, mingo@elte.hu, s0mbre@tservice.net.ru, a.p.zijlstra@chello.nl, LKML , Netdev , efault@gmx.de, Andrew Morton Subject: Re: [tbench regression fixes]: digging out smelly deadmen. In-Reply-To: <20081031.025159.51432990.davem@davemloft.net> Message-ID: References: <20081031.005219.141937694.davem@davemloft.net> <20081031.025159.51432990.davem@davemloft.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-696208474-2137390123-1225449754=:7072" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2031 Lines: 63 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---696208474-2137390123-1225449754=:7072 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Fri, 31 Oct 2008, David Miller wrote: > From: "Ilpo J?rvinen" > 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? Effectively its this: signal(SIGALRM, alarm_handler); ... while (flag) { /* flagged by alarm_handler */ loops = 90 open & setup sockets & connection while (--loops > 0) { write(wr_fd, buf, size); read(rd_fd, buf, size); } close sockets } where size comes from this array (advancing in the inner loop one by one): static int sizes[] = { 1, 3, 5, 7, 16, 32, 64, 512, 1024, 2048, /* misc. sizes */ 1, 3, 5, 7, 16, 32, 64, 512, 1024, 2048, 32, 32, 32, 32, 32, 32, /* x windows mostly... */ 512, 512, 512, 512, 512, /* DBMS's mostly */ }; buf sits in the stack and is not initialized (besides reading into it). ...I think the rest is just bogus complexity :-) ...maybe I should just take that from above as basis for Reduced AIM9 benchmark, it nearly compiles already. > If hash chain conflicts do happen for those 2 sockets, just traversing > the chain 2 entries deep could show up. No idea on this one. -- i. ---696208474-2137390123-1225449754=:7072-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/