From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>,
honnappa.nagarahalli@arm.com, jerinj@marvell.com,
Chao Zhu <chaozhu@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2] Add 'try' semantics for RD and WR locking
Date: Wed, 19 Dec 2018 03:39:40 +0100 [thread overview]
Message-ID: <3706402.B1puXbZNJX@xps> (raw)
In-Reply-To: <1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com>
13/11/2018 18:27, Konstantin Ananyev:
> 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
Any comment?
next prev parent reply other threads:[~2018-12-19 2:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 17:27 [PATCH 0/2] Add 'try' semantics for RD and WR locking Konstantin Ananyev
2018-11-13 17:27 ` [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 ` [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 ` Thomas Monjalon [this message]
2018-12-19 18:07 ` [PATCH v2 0/2] Add 'try' semantics for RD and WR locking Konstantin Ananyev
2018-12-19 19:53 ` Thomas Monjalon
2018-12-19 18:07 ` [PATCH v2 1/2] rwlock: introduce " Konstantin Ananyev
2018-12-19 18:07 ` [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=3706402.B1puXbZNJX@xps \
--to=thomas@monjalon.net \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.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.