If you see my first mail, I have mentioned that gcc has support for atomic builtins, which can be used to support atomic behaviour. You can refer gcc’s documentation for the same at https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gcc/_005f_005fsync-Builtins.html#g_t_005f_005fsync-Builtins <https://gcc.gnu.org/onlinedocs/gcc-5.2.0/gcc/_005f_005fsync-Builtins.html#g_t_005f_005fsync-Builtins>
> On 13-Sep-2019, at 10:10 PM, Rhodri James <rho...@kynesim.co.uk> wrote: > > On 13/09/2019 17:31, Vinay Sharma wrote: >> multiprocessing.Value can be synchronised using a lock, but if I have >> multiple multiprocessing.Value(s) which I want to synchronise between two >> processes, then I will have to pass a lock for each multiprocessing.Value. >> Therefore having a multiprocessing.AtomicValue could prove handy in these >> cases. > > I repeat, how does this work? If you want atomicity across processes, you > need some kind of lock at some level. > > -- > Rhodri James *-* Kynesim Ltd
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/LZL2YN5E6UXWG2KZVIAAMER5HB6D7TXY/ Code of Conduct: http://python.org/psf/codeofconduct/
