From: Thomas Monjalon <thomas@monjalon.net>
To: Joyce Kong <joyce.kong@arm.com>, gavin.hu@arm.com
Cc: dev@dpdk.org, nd@arm.com, jerinj@marvell.com,
konstantin.ananyev@intel.com, chaozhu@linux.vnet.ibm.com,
bruce.richardson@intel.com, hemant.agrawal@nxp.com,
honnappa.nagarahalli@arm.com
Subject: Re: [PATCH v5 0/3] rwlock: reimplement rwlock with atomic and add relevant perf test case
Date: Thu, 28 Mar 2019 11:50:34 +0100 [thread overview]
Message-ID: <2011061.iOykufG12a@xps> (raw)
In-Reply-To: <1553505299-34459-1-git-send-email-joyce.kong@arm.com>
> Gavin Hu (1):
> rwlock: reimplement with atomic builtins
>
> Joyce Kong (2):
> test/rwlock: add perf test case on all available cores
> test/rwlock: amortize the cost of getting time
Applied, thanks
next prev parent reply other threads:[~2019-03-28 10:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 3:37 [PATCH v1 0/2] reimplement rwlock and add relevant perf test case Joyce Kong
2018-12-13 3:37 ` [PATCH v1 1/2] test/rwlock: add " Joyce Kong
2018-12-19 23:34 ` Ananyev, Konstantin
2018-12-20 1:01 ` Gavin Hu (Arm Technology China)
2018-12-20 1:45 ` Honnappa Nagarahalli
2019-03-14 13:15 ` [PATCH v3 0/3] rwlock: reimplement rwlock with atomic and add relevant " Joyce Kong
2019-03-14 13:15 ` [PATCH v3 1/3] rwlock: reimplement with atomic builtins Joyce Kong
2019-03-14 15:54 ` Stephen Hemminger
2019-03-15 3:04 ` Gavin Hu (Arm Technology China)
2019-03-15 11:41 ` Ananyev, Konstantin
2019-03-19 8:31 ` Gavin Hu (Arm Technology China)
2019-03-14 13:15 ` [PATCH v3 2/3] test/rwlock: add perf test case on all available cores Joyce Kong
2019-03-14 13:15 ` [PATCH v3 3/3] test/rwlock: amortize the cost of getting time Joyce Kong
2019-03-14 15:02 ` Honnappa Nagarahalli
2019-03-20 6:25 ` [PATCH v4 0/3] rwlock: reimplement rwlock with atomic and add relevant perf test case Joyce Kong
2019-03-20 6:25 ` [PATCH v4 1/3] rwlock: reimplement with atomic builtins Joyce Kong
2019-03-21 18:43 ` Ananyev, Konstantin
2019-03-25 9:18 ` Joyce Kong (Arm Technology China)
2019-03-20 6:25 ` [PATCH v4 2/3] test/rwlock: add perf test case on all available cores Joyce Kong
2019-03-21 18:44 ` Ananyev, Konstantin
2019-03-20 6:25 ` [PATCH v4 3/3] test/rwlock: amortize the cost of getting time Joyce Kong
2019-03-21 18:44 ` Ananyev, Konstantin
2019-03-25 9:14 ` [PATCH v5 0/3] rwlock: reimplement rwlock with atomic and add relevant perf test case Joyce Kong
2019-03-28 10:50 ` Thomas Monjalon [this message]
2019-04-16 14:57 ` [dpdk-dev] " Kevin Traynor
2019-03-25 9:14 ` [PATCH v5 1/3] rwlock: reimplement with atomic builtins Joyce Kong
2019-03-25 9:14 ` [PATCH v5 2/3] test/rwlock: add perf test case on all available cores Joyce Kong
2019-03-25 9:14 ` [PATCH v5 3/3] test/rwlock: amortize the cost of getting time Joyce Kong
2018-12-13 3:37 ` [PATCH v1 2/2] rwlock: reimplement with __atomic builtins Joyce Kong
2018-12-19 23:50 ` Ananyev, Konstantin
2018-12-13 5:27 ` [PATCH v1 0/2] reimplement rwlock and add relevant perf test case Stephen Hemminger
2018-12-14 1:30 ` Gavin Hu (Arm Technology China)
2018-12-17 5:16 ` Honnappa Nagarahalli
2018-12-19 20:37 ` Thomas Monjalon
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=2011061.iOykufG12a@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=joyce.kong@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.