Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756777AbZA2KYZ (ORCPT ); Thu, 29 Jan 2009 05:24:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751740AbZA2KYQ (ORCPT ); Thu, 29 Jan 2009 05:24:16 -0500 Received: from mail-in-03.arcor-online.net ([151.189.21.43]:49046 "EHLO mail-in-03.arcor-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751635AbZA2KYO (ORCPT ); Thu, 29 Jan 2009 05:24:14 -0500 X-DKIM: Sendmail DKIM Filter v2.6.0 mail-in-02.arcor-online.net 434E43FE7DA Subject: Re: [Bugme-new] [Bug 12562] New: High overhead while switching or synchronizing threads on different cores From: Thomas Pilarski To: Peter Zijlstra Cc: Andrew Morton , Mike Galbraith , Gregory Haskins , bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <1233223979.5294.41.camel@bugs-laptop> References: <20090128125604.94ed3fe0.akpm@linux-foundation.org> <1233181507.6988.14.camel@bugs-laptop> <1233220048.7835.19.camel@twins> <1233223979.5294.41.camel@bugs-laptop> Content-Type: text/plain Date: Thu, 29 Jan 2009 11:24:04 +0100 Message-Id: <1233224644.5294.52.camel@bugs-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 730 Lines: 25 Some explanation of the test program. ./schedulerissue 1 4096 8 2000 1 producer and 1 consumer buffer size of 4096 doubles * 8byte 8 buffer (256kB total buffer) 2000 messages ./schedulerissue 2 4096 8 2000 2 producer and 2 consumer buffer size of 4096 doubles * 8byte 8 buffer (256kB total buffer) 2000 messages It was not 512KB bytes in the test before, but 4MB. But there is the same problem with a total buffer size of 48kB and 4 threads (./schedulerissue 2 2048 3 20000). -- 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/