From: Huang Ying <ying.huang@intel.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: huang ying <huang.ying.caritas@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: About lock-less data structure patches
Date: Thu, 07 Apr 2011 10:14:08 +0800 [thread overview]
Message-ID: <4D9D1DF0.6030704@intel.com> (raw)
In-Reply-To: <20110406014824.GB32321@Krystal>
On 04/06/2011 09:48 AM, Mathieu Desnoyers wrote:
> * huang ying (huang.ying.caritas@gmail.com) wrote:
[snip]
>>>>
>>>> OK. I will change the comments, adding these semantics explanation.
>>>> The user should be warned :)
>>>
>>> Yes, that makes sense. After this generalization step, if you're ok with
>>> this, we could aim at moving the implementation from a stack to a queue
>>> and provide fifo semantic rather than lifo, so that other users (e.g.
>>> call_rcu in the kernel) can start benefiting from it.
>>
>> I think that is good to move from stack to queue.
>>
>> I will send out changed lock-less data structure patchset soon. And
>> we can continue to work on the new lock-less queue at the same time.
>
> Sounds like a very good plan! Thanks!
Maybe you can send out your lock-less queue patches, so we can work on that.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2011-04-07 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D928405.4050607@intel.com>
[not found] ` <20110329182145.e64b66b5.akpm@linux-foundation.org>
[not found] ` <4D9287C3.7030103@intel.com>
[not found] ` <20110330032203.GC21838@one.firstfloor.org>
[not found] ` <20110329202649.137a8a18.akpm@linux-foundation.org>
[not found] ` <20110330133411.GA11101@Krystal>
[not found] ` <BLU0-SMTP52616BFA7ABB7E8E73E8396BC0@phx.gbl>
2011-03-31 1:39 ` About lock-less data structure patches Huang Ying
2011-04-01 21:37 ` Mathieu Desnoyers
2011-04-02 5:05 ` Huang Ying
2011-04-04 15:53 ` Mathieu Desnoyers
2011-04-05 1:16 ` huang ying
2011-04-05 4:42 ` Mathieu Desnoyers
2011-04-05 12:46 ` huang ying
2011-04-06 1:48 ` Mathieu Desnoyers
2011-04-07 2:14 ` Huang Ying [this message]
2011-04-07 18:32 ` Mathieu Desnoyers
2011-04-07 22:05 ` Paul E. McKenney
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=4D9D1DF0.6030704@intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=huang.ying.caritas@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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