[petsc-dev] Naming for functions that are safe to call from threads

Barry Smith bsmith at mcs.anl.gov
Sat Feb 16 19:55:31 CST 2013


 _k   _t   ?


On Feb 16, 2013, at 7:06 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> 
> On Sat, Feb 16, 2013 at 6:52 PM, Matthew Knepley <knepley at gmail.com> wrote:
> Still like that better than _r.
> 
> Reentrancy is not a subset or superset of thread-safety. I certainly wasn't suggesting that we use _r to indicate thread-safety. Rather, I was asking whether we should use a shorter (possibly single-character) identifier, and perhaps something that indicated "CPU threads" so as not to confuse with device kernels.




More information about the petsc-dev mailing list