linux-kernel - Re: About lock-less data structure patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 07 Apr 2011 10:14:08 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
CC:	huang ying <huang.ying.caritas@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: About lock-less data structure patches

On 04/06/2011 09:48 AM, Mathieu Desnoyers wrote:
> * huang ying (huang.ying.caritas@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/