Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754557AbbFSPvQ (ORCPT ); Fri, 19 Jun 2015 11:51:16 -0400 Received: from g9t5008.houston.hp.com ([15.240.92.66]:38008 "EHLO g9t5008.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753765AbbFSPvE (ORCPT ); Fri, 19 Jun 2015 11:51:04 -0400 From: Waiman Long To: Peter Zijlstra , Ingo Molnar , Arnd Bergmann Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Will Deacon , Scott J Norton , Douglas Hatch , Waiman Long Subject: [PATCH v5 0/3] locking/qrwlock: More optimizations in qrwlock Date: Fri, 19 Jun 2015 11:49:59 -0400 Message-Id: <1434729002-57724-1-git-send-email-Waiman.Long@hp.com> X-Mailer: git-send-email 1.7.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1281 Lines: 38 v4->v5: - Add a new patch to rename function names to sync up to qspinlock naming convention. - Move the extended qrwlock structure to the header file as requested by Will Deacon so that it can also be used in the ARM's architecture specific code. v3->v4: - Remove the unnecessary _QW_WMASK check in queue_read_lock_slowpath(). v2->v3: - Fix incorrect commit log message in patch 1. v1->v2: - Add microbenchmark data for the second patch This patch set contains 2 patches on qrwlock. The first one is to optimize the interrupt context reader slowpath. The second one is to optimize the writer slowpath. *** BLURB HERE *** Waiman Long (3): locking/qrwlock: Rename functions to queued_*() locking/qrwlock: Better optimization for interrupt context readers locking/qrwlock: Don't contend with readers when setting _QW_WAITING arch/x86/include/asm/qrwlock.h | 7 ++-- include/asm-generic/qrwlock.h | 58 +++++++++++++++++----------------- include/asm-generic/qrwlock_types.h | 18 ++++++++++- kernel/locking/qrwlock.c | 29 ++++++++--------- 4 files changed, 63 insertions(+), 49 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/