Re: [PATCH v8 3/6] MCS Lock: optimizations and extra comments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2014-01-21 at 13:01 -0800, Jason Low wrote:
> /*
>  * Lock acquired, don't need to set node->locked to 1. Threads
>  * only spin on its own node->locked value for lock acquisition.
>  * However, since this thread can immediately acquire the lock
>  * and does not proceed to spin on its own node->locked, this
>  * value won't be used. If a debug mode is needed to
>  * audit lock status, then set node->locked value here.
>  */ 

I'll update the comment accordingly.

Tim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]