From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx109.postini.com [74.125.245.109]) by kanga.kvack.org (Postfix) with SMTP id C6F636B006C for ; Thu, 18 Apr 2013 22:43:01 -0400 (EDT) Message-ID: <5170AF2B.80600@linux.intel.com> Date: Thu, 18 Apr 2013 19:42:51 -0700 From: Darren Hart MIME-Version: 1.0 Subject: Re: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage References: <516EAF31.8000107@linux.intel.com> <516EBF23.2090600@sr71.net> <516EC508.6070200@linux.intel.com> <51700475.7050102@linux.intel.com> In-Reply-To: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: zhang.yi20@zte.com.cn Cc: Dave Hansen , Dave Hansen , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Ingo Molnar , Peter Zijlstra , Thomas Gleixner On 04/18/2013 07:13 PM, zhang.yi20@zte.com.cn wrote: > Darren Hart wrote on 2013/04/18 22:34:29: > >> On 04/18/2013 01:05 AM, zhang.yi20@zte.com.cn wrote: >>> >>> I have run futextest/performance/futex_wait for testing, >>> 5 times before make it long: >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10215 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 9862 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10081 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10060 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10081 Kiter/s >>> >>> >>> And 5 times after make it long: >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 9940 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10204 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 9901 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10152 Kiter/s >>> >>> futex_wait: Measure FUTEX_WAIT operations per second >>> Arguments: iterations=100000000 threads=256 >>> Result: 10060 Kiter/s >>> >>> >>> Seems OK, is it? >>> >> >> Changes appear to be in the noise, no impact with this load >> anyway. >> How many CPUs on your test machine? I presume not 256? >> >> -- > > There are 16 CPUsGBP! and mode is: > Intel(R) Xeon(R) CPU C5528 @ 2.13GHz > > Shall I make the number of threads as the CPUS? I test again with argument > '-n 16', the result is similar. No, I just wanted to be sure you weren't running 256 threads on 1 CPU as you wouldn't be likely to be stressing the bucket list much :-) > BTW, have you seen the testcase in my other mail? It seems to be rejected > by LKML. Might have something to do with what appears to still be HTML email. You really need to fix your email client. See: http://www.tux.org/lkml/ #12 in particular. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org