From: "Dementiev, Roman" <roman.dementiev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] add support for HTM lock elision for x86
Date: Tue, 2 Jun 2015 13:17:07 +0000 [thread overview]
Message-ID: <4EB94430E0E05A4EAE258E2A9A1B98DD33EAE0D3@irsmsx110.ger.corp.intel.com> (raw)
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
From rolette@infiniteio.com Tue Jun 2 15:21:24 2015
Return-Path: <rolette@infiniteio.com>
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com
[209.85.212.182]) by dpdk.org (Postfix) with ESMTP id B03FBBDC2
for <dev@dpdk.org>; Tue, 2 Jun 2015 15:21:24 +0200 (CEST)
Received: by wizo1 with SMTP id o1so144374926wiz.1
for <dev@dpdk.org>; Tue, 02 Jun 2015 06:21:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d\x1e100.net; s 130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=EZ5V09Uf0HqR5pepp3xmM2K+ESwvO6YmUxphj1p/FH4=;
b=KSmNxWms+vaLWfI43mVrAVKs9hjo5OOHZj8i/fWcPZBQdx7OF1WZqsohu1JQL/p5c2
4wxywVCESWJefU+OtJ4aluXRwJMbKZaX6KGPS9yNIEkXffuZhxri5VkEzyig3Cz6FzZg
vMEvsEiVcO3b40xPZ/KtVENZ1AXE48EeeXwvlcpKNzbSittMT2qxJvWqIFtWIhHyZz2G
LXZ7WdpwSYhyobXxFX/kMMe2n/qDqlAvgo+pIgf0jZdJVBTqz/2Mx8MdJQlCz2BQbzpv
KyylO/bE46ktW7D8eQVKtBMtykrW1svCYCebSYLEiWD9PA/Mlq+g59HV7uOBjpR0LRag
JHDw=X-Gm-Message-State: ALoCoQnTMgOKUua0wm5br0wzyd2vyF1dbh6JeCzRCh1zTNb0jX61HFls8jGfZRV8ah0sjrcDwWll
MIME-Version: 1.0
X-Received: by 10.195.18.8 with SMTP id gi8mr11293724wjd.153.1433251284551;
Tue, 02 Jun 2015 06:21:24 -0700 (PDT)
Received: by 10.194.36.193 with HTTP; Tue, 2 Jun 2015 06:21:24 -0700 (PDT)
In-Reply-To: <1433250693-23644-1-git-send-email-roman.dementiev@intel.com>
References: <1433250693-23644-1-git-send-email-roman.dementiev@intel.com>
Date: Tue, 2 Jun 2015 08:21:24 -0500
Message-ID: <CADNuJVpeKa9-R7WHkoCzw82vpYd=3XmhOoz2JfGsFLzDW+F5UQ@mail.gmail.com>
From: Jay Rolette <rolette@infiniteio.com>
To: Roman Dementiev <roman.dementiev@intel.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] 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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
<mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
<mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2015 13:21:24 -0000
On Tue, Jun 2, 2015 at 8:11 AM, Roman Dementiev <roman.dementiev@intel.com>
wrote:
>
> 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 very interesting. Do you have any summary you can give us of what
the performance implications are from your test data?
> This is not a replacement for lock usages since not all critical sections
> protected
> by locks are friendly to HTM.
>
Any pointers to material that describe where HTM in its current incarnation
on x86 is approprate?
>
> 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
>
> app/test/Makefile | 1 +
> app/test/test_hash_scaling.c | 223
> +++++++++++++++++++++
> lib/librte_eal/common/Makefile | 4 +-
> .../common/include/arch/ppc_64/rte_rwlock.h | 38 ++++
> .../common/include/arch/ppc_64/rte_spinlock.h | 41 ++++
> lib/librte_eal/common/include/arch/x86/rte_rtm.h | 73 +++++++
> .../common/include/arch/x86/rte_rwlock.h | 82 ++++++++
> .../common/include/arch/x86/rte_spinlock.h | 107 ++++++++++
> lib/librte_eal/common/include/generic/rte_rwlock.h | 194
> ++++++++++++++++++
> .../common/include/generic/rte_spinlock.h | 75 +++++++
> lib/librte_eal/common/include/rte_rwlock.h | 158 ---------------
> 11 files changed, 836 insertions(+), 160 deletions(-)
>
Thanks!
Jay
next reply other threads:[~2015-06-02 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:17 Dementiev, Roman [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-02 13:11 Roman Dementiev
[not found] ` <CADNuJVpeKa9-R7WHkoCzw82vpYd=3XmhOoz2JfGsFLzDW+F5UQ@mail.gmail.com>
2015-06-02 13:39 ` Dementiev, Roman
2015-06-02 14:55 ` Roman Dementiev
2015-06-03 18:40 ` Stephen Hemminger
2015-06-05 15:12 ` Roman Dementiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB94430E0E05A4EAE258E2A9A1B98DD33EAE0D3@irsmsx110.ger.corp.intel.com \
--to=roman.dementiev@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).