From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] Add 'try' semantics for RD and WR locking
Date: Tue, 13 Nov 2018 17:27:39 +0000 [thread overview]
Message-ID: <1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com> (raw)
This series targets 19.02 release
Introduce rte_rwlock_read_trylock() and rte_rwlock_write_trylock()
and new UT test-case for it.
Konstantin Ananyev (2):
rwlock: introduce 'try' semantics for RD and WR locking
test: add new test-cases for rwlock autotest
.../common/include/generic/rte_rwlock.h | 54 +++
lib/librte_eal/rte_eal_version.map | 2 +
test/test/test_rwlock.c | 405 +++++++++++++++++-
3 files changed, 442 insertions(+), 19 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-13 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 17:27 Konstantin Ananyev [this message]
2018-11-13 17:27 ` [dpdk-dev] [PATCH 1/2] rwlock: introduce " Konstantin Ananyev
2018-12-19 6:37 ` Honnappa Nagarahalli
2018-12-19 8:30 ` Gavin Hu (Arm Technology China)
2018-12-19 10:28 ` Mattias Rönnblom
2018-12-19 10:56 ` Ananyev, Konstantin
2018-12-19 11:00 ` Bruce Richardson
2018-12-19 12:41 ` Ananyev, Konstantin
2018-12-19 15:11 ` Honnappa Nagarahalli
2018-12-19 16:27 ` Ananyev, Konstantin
2018-11-13 17:27 ` [dpdk-dev] [PATCH 2/2] test: add new test-cases for rwlock autotest Konstantin Ananyev
2018-12-19 8:28 ` Gavin Hu (Arm Technology China)
2018-12-19 2:39 ` [dpdk-dev] [PATCH 0/2] Add 'try' semantics for RD and WR locking Thomas Monjalon
2018-12-19 18:07 ` [dpdk-dev] [PATCH v2 " Konstantin Ananyev
2018-12-19 19:53 ` Thomas Monjalon
2018-12-19 18:07 ` [dpdk-dev] [PATCH v2 1/2] rwlock: introduce " Konstantin Ananyev
2018-12-19 18:07 ` [dpdk-dev] [PATCH v2 2/2] test: add new test-cases for rwlock autotest Konstantin Ananyev
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=1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@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).