From: Carlos O'Donell <carlos@redhat.com>
To: "Wang, Kemi" <kemi.wang@intel.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Florian Weimer <fweimer@redhat.com>, Rical Jason <rj@2c3t.io>,
Glibc alpha <libc-alpha@sourceware.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
"Chen, Tim C" <tim.c.chen@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
"Lu, Aaron" <aaron.lu@intel.com>,
"Li, Aubrey" <aubrey.li@intel.com>
Subject: Re: [RFC 0/4] Add a new mutex type PTHREAD_MUTEX_QUEUESPINNER_NP
Date: Fri, 06 Jul 2018 16:17:00 -0000 [thread overview]
Message-ID: <726b368c-ec10-999f-8ad5-a5c4444f5b73@redhat.com> (raw)
In-Reply-To: <25017BF213203E48912DB000DE5F5E1E6B834079@SHSMSX101.ccr.corp.intel.com>
On 07/06/2018 11:56 AM, Wang, Kemi wrote:
>> Given that distributions could backport this (no new symbols, just
>> a new flag), is there really any rush in getting it reviewed?
>
> To be honest, yes, please. And I will respond your feedback ASAP.
This sounds mysterious. Why are you in a rush?
--
Cheers,
Carlos.
prev parent reply other threads:[~2018-07-06 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 8:16 Kemi Wang
2018-07-02 8:16 ` [PATCH 4/4] Manual: Add manual for pthread mutex Kemi Wang
2018-07-02 8:17 ` [PATCH 1/4] Mutex: Queue spinners to reduce cache line bouncing and ensure fairness Kemi Wang
2018-07-02 8:17 ` [PATCH 3/4] BENCHMARK: add a benchmark for testing new type of mutex Kemi Wang
2018-07-02 8:17 ` [PATCH 2/4] Mutex: add unit tests for new type Kemi Wang
2018-07-05 20:12 ` [RFC 0/4] Add a new mutex type PTHREAD_MUTEX_QUEUESPINNER_NP Carlos O'Donell
2018-07-06 1:35 ` kemi
2018-07-06 7:46 ` kemi
2018-07-06 12:42 ` Carlos O'Donell
2018-07-06 15:56 ` Wang, Kemi
2018-07-06 16:17 ` Carlos O'Donell [this message]
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=726b368c-ec10-999f-8ad5-a5c4444f5b73@redhat.com \
--to=carlos@redhat.com \
--cc=aaron.lu@intel.com \
--cc=adhemerval.zanella@linaro.org \
--cc=andi.kleen@intel.com \
--cc=aubrey.li@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fweimer@redhat.com \
--cc=kemi.wang@intel.com \
--cc=libc-alpha@sourceware.org \
--cc=rj@2c3t.io \
--cc=tim.c.chen@intel.com \
--cc=ying.huang@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).