Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp877636img; Fri, 22 Mar 2019 10:26:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqz+zJbURmGn5T4hQ9ne5gt3ecQA3zpimpbAVVl0CKvaiqLVsk5/Fdlw4Qd7ui58ygA37iuJ X-Received: by 2002:a65:508b:: with SMTP id r11mr10077379pgp.242.1553275595098; Fri, 22 Mar 2019 10:26:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553275595; cv=none; d=google.com; s=arc-20160816; b=pm3wBgrLx/2W+mv0QP+zrF8noaTKIt+WvzzZiV2l7mB9VTMo2XPjno2Pvyf4Cw7akV WAx0Ygo8uce0Pwri171fuQPuvVRSYirZKAx8q6fq+NviTZqHSxhUmzsPV61M2RevRsLN I8ACokwXgA5ZuknkZcTLGlBSrZZFzejSOfDrddVDxU9s0axr/pza9WTLmRFTgHZ6Esm1 9bFzipegseFGRvyW8qtI3GLKuDh+Fg4Hcl9x4pc4r1nIpGKDoF1A5cMPy16u1kpJyuEx hh9Loo5s3kYZ+opI6TtmjvavHbWS1FBSbWS3mFVB5e8E8SVNl9+gJDF+bKFWht/vMPWa 3tQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=oETpZyH7xLKUdQHFKiHuSJuVBCjYUIIZETTJzqHKcsc=; b=JFcXa52FVtmooqOEccMFIfdJ2URxs9DKZSSLi2HyYLg9d2/aWSsKoYRjh1AKmfYxDc MuPNwqSuIEgpuugodnA7YhzyUEraGkdVKYNu9QUPVZngE8mdPAqwhzkvKD4SwUY3CizB GNr4T5h6e2dxCfufXT0ZIrTRV3pWpJVTVz+viUueYrZS1q3EJFboLX9y+QkwqUC+gjHP oKQA+ovdCbWrNhJdOPXJFpPcM89tBMCaU3WiB0pGba8RVd2xBOqtkJbi2ElN4jf2RJh+ 2VphgOTlSgBA+/g8K+dcaP7Vhc5cO4Aqn0XRH8l1+S+EzfDMWK/uFWix1FYO7uWcr+KV Ifkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b="ZVItmiS/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d24si7383044pls.83.2019.03.22.10.26.16; Fri, 22 Mar 2019 10:26:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b="ZVItmiS/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728672AbfCVRZa (ORCPT + 99 others); Fri, 22 Mar 2019 13:25:30 -0400 Received: from pandora.armlinux.org.uk ([78.32.30.218]:37782 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727741AbfCVRZ3 (ORCPT ); Fri, 22 Mar 2019 13:25:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=oETpZyH7xLKUdQHFKiHuSJuVBCjYUIIZETTJzqHKcsc=; b=ZVItmiS/eWU+t+u/Ypr3JsIfH K7gIVIjf/tMjHU4ClkIDbVc0xR0NNLF0n2wa84s5q/gE/RJhZVCvd6fK2BNDfxu1OEk0mYW6Lxe7q sC878zm3M3R4xuyn5EQKV8utKNN6YSO3kcgC8Z2P6R2io6qHXXWUfM93/Ov1/3+ISTVKCxVxfdeDX PVBv72GKBfeUmK+m8QEwUJ4ZgLNUaSU3cKPuLzRsEu+5uvRBLZJnNeejkUlyxFeYXi169VW+wjQc0 N/vQusiIGyjYjOyaXtJOkcSeuERNZ5lHhz/nfZftS80Z3QEJEyuhGvEhBze/s0OwRLKs+0Mt+5wAq NBOeDpgHA==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:55184) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1h7Nus-0002MI-Vr; Fri, 22 Mar 2019 17:25:15 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.89) (envelope-from ) id 1h7Nuf-0000lO-F7; Fri, 22 Mar 2019 17:25:01 +0000 Date: Fri, 22 Mar 2019 17:25:01 +0000 From: Russell King - ARM Linux admin To: Waiman Long Cc: Peter Zijlstra , Ingo Molnar , Will Deacon , Thomas Gleixner , linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, linux-mips@vger.kernel.org, "H. Peter Anvin" , sparclinux@vger.kernel.org, linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, Davidlohr Bueso , linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, x86@kernel.org, uclinux-h8-devel@lists.sourceforge.jp, linux-xtensa@linux-xtensa.org, Arnd Bergmann , linux-um@lists.infradead.org, linux-m68k@lists.linux-m68k.org, openrisc@lists.librecores.org, Borislav Petkov , linux-arm-kernel@lists.infradead.org, Tim Chen , linux-parisc@vger.kernel.org, Linus Torvalds , linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, nios2-dev@lists.rocketboards.org, Andrew Morton , linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v5 3/3] locking/rwsem: Optimize down_read_trylock() Message-ID: <20190322172501.3nbjw6e2wqsaisgw@shell.armlinux.org.uk> References: <20190322143008.21313-1-longman@redhat.com> <20190322143008.21313-4-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190322143008.21313-4-longman@redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 22, 2019 at 10:30:08AM -0400, Waiman Long wrote: > Modify __down_read_trylock() to optimize for an unlocked rwsem and make > it generate slightly better code. > > Before this patch, down_read_trylock: > > 0x0000000000000000 <+0>: callq 0x5 > 0x0000000000000005 <+5>: jmp 0x18 > 0x0000000000000007 <+7>: lea 0x1(%rdx),%rcx > 0x000000000000000b <+11>: mov %rdx,%rax > 0x000000000000000e <+14>: lock cmpxchg %rcx,(%rdi) > 0x0000000000000013 <+19>: cmp %rax,%rdx > 0x0000000000000016 <+22>: je 0x23 > 0x0000000000000018 <+24>: mov (%rdi),%rdx > 0x000000000000001b <+27>: test %rdx,%rdx > 0x000000000000001e <+30>: jns 0x7 > 0x0000000000000020 <+32>: xor %eax,%eax > 0x0000000000000022 <+34>: retq > 0x0000000000000023 <+35>: mov %gs:0x0,%rax > 0x000000000000002c <+44>: or $0x3,%rax > 0x0000000000000030 <+48>: mov %rax,0x20(%rdi) > 0x0000000000000034 <+52>: mov $0x1,%eax > 0x0000000000000039 <+57>: retq > > After patch, down_read_trylock: > > 0x0000000000000000 <+0>: callq 0x5 > 0x0000000000000005 <+5>: xor %eax,%eax > 0x0000000000000007 <+7>: lea 0x1(%rax),%rdx > 0x000000000000000b <+11>: lock cmpxchg %rdx,(%rdi) > 0x0000000000000010 <+16>: jne 0x29 > 0x0000000000000012 <+18>: mov %gs:0x0,%rax > 0x000000000000001b <+27>: or $0x3,%rax > 0x000000000000001f <+31>: mov %rax,0x20(%rdi) > 0x0000000000000023 <+35>: mov $0x1,%eax > 0x0000000000000028 <+40>: retq > 0x0000000000000029 <+41>: test %rax,%rax > 0x000000000000002c <+44>: jns 0x7 > 0x000000000000002e <+46>: xor %eax,%eax > 0x0000000000000030 <+48>: retq > > By using a rwsem microbenchmark, the down_read_trylock() rate (with a > load of 10 to lengthen the lock critical section) on a x86-64 system > before and after the patch were: > > Before Patch After Patch > # of Threads rlock rlock > ------------ ----- ----- > 1 14,496 14,716 > 2 8,644 8,453 > 4 6,799 6,983 > 8 5,664 7,190 > > On a ARM64 system, the performance results were: > > Before Patch After Patch > # of Threads rlock rlock > ------------ ----- ----- > 1 23,676 24,488 > 2 7,697 9,502 > 4 4,945 3,440 > 8 2,641 1,603 > > For the uncontended case (1 thread), the new down_read_trylock() is a > little bit faster. For the contended cases, the new down_read_trylock() > perform pretty well in x86-64, but performance degrades at high > contention level on ARM64. So, 70% for 4 threads, 61% for 4 threads - does this trend continue tailing off as the number of threads (and cores) increase? -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up