From: pbonzini@redhat.com (Paolo Bonzini)
Subject: [ltt-dev] [RFC PATCHv2 4/5] urcu: re-implment urcu-qsbr
Date: Tue, 30 Aug 2011 10:25:33 +0200 [thread overview]
Message-ID: <4E5C9E7D.2080501@redhat.com> (raw)
In-Reply-To: <4E5C5141.1050103@cn.fujitsu.com>
On 08/30/2011 04:56 AM, Lai Jiangshan wrote:
> When readers> cores, the n_updates is very unstable, so the result of n_updates makes less sense.
>
> The result show Paolo's patch has advance,
> but my patch has more advance for reader site performance.
No doubt about that---we're just looking for the right abstraction for
your patch.
Do you have a pointer to a paper or something explaining the "proxy
lock" concept?
Paolo
next parent reply other threads:[~2011-08-30 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1314003233.git.laijs@cn.fujitsu.com>
[not found] ` <7a284c3769a00c1e3c859d39b51fa77e07d785ea.1314003233.git.laijs@cn.fujitsu.com>
[not found] ` <4E55E5BB.3000608@cn.fujitsu.com>
[not found] ` <4E55ECAE.8030804@redhat.com>
[not found] ` <4E56011C.30100@cn.fujitsu.com>
[not found] ` <4E560952.3070809@redhat.com>
[not found] ` <4E5B06C8.3060108@cn.fujitsu.com>
[not found] ` <20110829125603.GB10228@Krystal>
[not found] ` <4E5C5141.1050103@cn.fujitsu.com>
2011-08-30 8:25 ` Paolo Bonzini [this message]
2011-08-30 10:53 ` Mathieu Desnoyers
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=4E5C9E7D.2080501@redhat.com \
--to=pbonzini@redhat.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