Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755974AbYHYJt0 (ORCPT ); Mon, 25 Aug 2008 05:49:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753600AbYHYJtR (ORCPT ); Mon, 25 Aug 2008 05:49:17 -0400 Received: from gv-out-0910.google.com ([216.239.58.189]:12316 "EHLO gv-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753554AbYHYJtQ (ORCPT ); Mon, 25 Aug 2008 05:49:16 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=rzHIq78MvRM+qK0aoAtbr/Br33ubGQ+a7q/C7YzwcfsRyRKqYJtx55j/HC97+Ygb7b i1n+MLknSk0eV6aT3aGrzB/xMoaipzyGwBWndbO+k6F34WPxUYzXvXOOYYOZ9ZPtYnto KFUKqxskusXv9iLL2kbNleE2rULdCrULokLTI= Message-ID: <48B28015.3040602@gmail.com> Date: Mon, 25 Aug 2008 12:49:09 +0300 From: =?UTF-8?B?VMO2csO2ayBFZHdpbg==?= User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Peter Zijlstra CC: Ingo Molnar , rml@tech9.net, Linux Kernel , "Thomas Gleixner mingo@redhat.com" , "H. Peter Anvin" Subject: Re: Quad core CPUs loaded at only 50% when running a CPU and mmap intensive multi-threaded task References: <48B1CC15.2040006@gmail.com> <1219643476.20732.1.camel@twins> <48B25988.8040302@gmail.com> <1219656190.8515.7.camel@twins> In-Reply-To: <1219656190.8515.7.camel@twins> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2628 Lines: 68 On 2008-08-25 12:23, Peter Zijlstra wrote: > On Mon, 2008-08-25 at 10:04 +0300, edwin wrote: > >> Peter Zijlstra wrote: >> >>> On Mon, 2008-08-25 at 00:01 +0300, Török Edwin wrote: >>> >>> >>>> Hi Ingo, >>>> >>>> When I run clamd (www.clamav.net), I can only get to load my CPU 50% >>>> (according to top), and disks at 30% (according to iostat -x 3), >>>> regardless how many threads I set (I tried 4, 8, 16, 32). >>>> >>>> >>> Can you share your .config, and prehaps tell what kernel version did >>> work for you? >>> >> Sorry, I forgot to include the .config, its at the end of this mail (the >> cfs debug info output included the .config though) >> >> Well, I just bought this new box, so there isn't a kernel version that I >> know that worked on this hardware (but I am trying to boot some older >> versions now). >> However on my previous box (Athlon64, non-SMP) I have never seen such a >> problem (that the CPU is loaded only 50% with clamd) and I've been >> running 2.6.26 and 2.6.27-rc4 there too. >> >> Details below, short summary here: >> 2.6.24: WORKS, clamd 400% CPU, testprogram runs in 27.4 seconds, 67% CPU >> load; and 28.5 seconds w/o setting affinity >> 2.6.25+: DOES NOT WORK, clamd 200%-300% CPU, testprogram runs in 38-40 >> seconds, 48-48% CPU load, and 47-56 seconds w/o setting affinity >> >> Debian has 2.6.18, 2.6.22, 2.6.24, 2.6.25, 2.6.26. >> 2.6.22 won't work with my lvm, so I can't boot that, so I tried 2.6.24: >> >> 2.6.24 doesn't have sched_debug enabled in the stock kernel >> unfortunately, but the output of cfs-debug-info.sh is available here, >> maybe it contains some useful info: >> http://edwintorok.googlepages.com/testrun-1219645937.tar.gz >> >> Is this enough info for you to reproduce the problem, or do you want me >> to try and bisect? >> > > No, I think I know what's going on.. > > mmap() and munmap() need to take the mmap_sem for writing (since they > modify the memory map) and you let each thread (one for each cpu) take > that process wide lock, twice, for a million times. > Are you referring to the mmap_sem lock, or my mutex lock around all_thread_time? > Guess what happens ;-) So the problem is that doing mmap() doesn't scale well with multiple threads, because there is contention on mmap_sem? Why did 2.6.24 seem to work better? Best regards, --Edwin -- 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/