From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 2ED04C850 for ; Fri, 19 Jun 2015 16:39:09 +0200 (CEST) Received: by wgbhy7 with SMTP id hy7so91452586wgb.2 for ; Fri, 19 Jun 2015 07:39:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=layuZ1tw5of+m4W23nvQ1lz4wlvIpOFegqJaMtsd+dI=; b=NHvdTQMbK4IBXnoIr3xLank4LhxdKgLjKa8G2nvHYGNbkzUBKkMiokOBWO2p8nIGnw Q+ueWjnmeD6Wa5EytG9sNl0F/tKzlEre0jSMqXOohADCzUboso9HsSfxJtkti2I3c7so UsOj/LyxtjlztZh4avmP6yNGJFQLdxIOAHQCvp0EPoiPgqwLAtnaO9m2uI4elC8vRy/D sDUxY8tThYJ1XjkSX95F4NN6O75LsSwAe/a/WC2AfexG92sq32NKragN6d05fDabBkX6 Y+Gtc2x8hTvwQm7A0JYn2a6+ld681BEfEs6el3OoPfN1bsToAzZ3uOlj31TABBcyRIyE aqXg== X-Gm-Message-State: ALoCoQlEhv0v2IBIoF846G6I//K4lnq9M36cyt/ZvEgToyfPfiXfQ8tbd3UtkMBhbkRs/+QQ3pxI X-Received: by 10.180.81.3 with SMTP id v3mr7193835wix.36.1434724749090; Fri, 19 Jun 2015 07:39:09 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id s10sm17350165wjy.35.2015.06.19.07.39.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Jun 2015 07:39:08 -0700 (PDT) From: Thomas Monjalon To: Roman Dementiev Date: Fri, 19 Jun 2015 16:38:06 +0200 Message-ID: <22085904.U2abn9Fdft@xps13> Organization: 6WIND User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; ) In-Reply-To: <1434712103-7500-1-git-send-email-roman.dementiev@intel.com> References: <1434475006-13732-1-git-send-email-roman.dementiev@intel.com> <1434712103-7500-1-git-send-email-roman.dementiev@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 0/3] add support for HTM lock elision for x86 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 14:39:09 -0000 2015-06-19 13:08, Roman Dementiev: > This series of patches adds methods that use hardware memory transactions (HTM) > on fast-path for DPDK locks (a.k.a. lock elision). Here the methods are > implemented for x86 using Restricted Transactional Memory instructions (Intel(r) > Transactional Synchronization Extensions). The implementation fall-backs to > the normal DPDK lock if HTM is not available or memory transactions fail. This > is not a replacement for ALL lock usages since not all critical sections > protected by locks are friendly to HTM. For example, an attempt to perform > a HW I/O operation inside a hardware memory transaction always aborts > the transaction since the CPU is not able to roll-back should the transaction > fail. Therefore, hardware transactional locks are not advised to be used around > rte_eth_rx_burst() and rte_eth_tx_burst() calls. > > Acked-by: Bruce Richardson > > v3 changes > -resolved a conflict in app/test/Makefile > -don't use angle brackets for rte_common.h include > > v2 changes > -added a documentation note about hardware limitations > > > Roman Dementiev (3): > spinlock: add support for HTM lock elision for x86 > rwlock: add support for HTM lock elision for x86 > test scaling of HTM lock elision protecting rte_hash Applied, thanks