search for: use_locking

...gcv* is: > > > > Issues: > > > > ** openblas 0.3.x x<7 is not thread safe if itself compiled for single thread > > use and then called from multiple threads (unlike the reference BLAS, say). > > 0.2.20 appears to be OK. For 0.3.x x>6 make USE_THREAD=0 USE_LOCKING=1 > > to make openblas ensures thread safety (currently unclear if USE_LOCKING > > will be default from 0.3.7). > > Does this mean that single-threaded openblas should be built with > USE_LOCKING=1 by default? Is there any upstream recommendation about > this? > &gt...

...erested, the issue Simon Wood reports with openblas and *mgcv* is: Issues: ** openblas 0.3.x x<7 is not thread safe if itself compiled for single thread use and then called from multiple threads (unlike the reference BLAS, say). 0.2.20 appears to be OK. For 0.3.x x>6 make USE_THREAD=0 USE_LOCKING=1 to make openblas ensures thread safety (currently unclear if USE_LOCKING will be default from 0.3.7). and running `mgcv:::blas.thread.test()` (Simon's non-exported function to test for problems) returns: > mgcv:::blas.thread.test() |...

On Wed, 27 May 2020 at 21:40, Gavin Simpson <ucfagls at gmail.com> wrote: > > Thanks I?aki, that is exactly what i was looking for, esp the last > option which I have now configured as an alias for easy remembering. > > I can answer the question re USE_LOCKING=1. I think that using both > those options is required to get thread-safety even if openblas was > compiled for single thread use. I don't know to what extent Simon has > engaged with upstream on this etc. I've seen that there is a brief note about this in the project's wiki....

Thanks I?aki, that is exactly what i was looking for, esp the last option which I have now configured as an alias for easy remembering. I can answer the question re USE_LOCKING=1. I think that using both those options is required to get thread-safety even if openblas was compiled for single thread use. I don't know to what extent Simon has engaged with upstream on this etc. All I know is that using the openblas shipped with Fedora for R is currently a recipe for disa...

...orts with openblas > and *mgcv* is: > > Issues: > > ** openblas 0.3.x x<7 is not thread safe if itself compiled for single thread > use and then called from multiple threads (unlike the reference BLAS, say). > 0.2.20 appears to be OK. For 0.3.x x>6 make USE_THREAD=0 USE_LOCKING=1 > to make openblas ensures thread safety (currently unclear if USE_LOCKING > will be default from 0.3.7). Does this mean that single-threaded openblas should be built with USE_LOCKING=1 by default? Is there any upstream recommendation about this? -- I?aki ?car

Thanks (again) I?aki. There was a typo in my reply above. I should have said: I *can't* answer the question re USE_LOCKING=1. Those other suggestions are really helpful too; I really didn't understand what the difference was (I'm still not clear what the differences are between say openblas-openmp and openblas-openmp64), but I did get R to pass mgcv's thread safe test with both openblas-openmp and blis-ope...

On Wed, 27 May 2020 at 23:03, Gavin Simpson <ucfagls at gmail.com> wrote: > > Thanks (again) I?aki. > > There was a typo in my reply above. I should have said: I *can't* > answer the question re USE_LOCKING=1. :) > Those other suggestions are really helpful too; I really didn't > understand what the difference was (I'm still not clear what the > differences are between say openblas-openmp and openblas-openmp64), > but I did get R to pass mgcv's thread safe test with both >...

...d a sms to my friends. I installed gammu. Pls see below for installed rpm. [root at mailgw ~]# rpm -qa |grep gammu gammu-1.11.0-1.el5.rf here's my /etc/gammurc file. [gammu] port = /dev/ttyUSB0 ;model = 6110 connection = dlr3 ;synchronizetime = yes ;logfile = gammulog ;logformat = textall ;use_locking = yes ;gammuloc = locfile ;startinfo = yes ;gammucoding = utf8 ;rsslevel = teststable ;usephonedb = yes [gammu1] port = /dev/ttyUSB1 ;model = 6110 connection = dlr3 ;synchronizetime = yes ;logfile = gammulog ;logformat = textall ;use_locking = yes ;gammuloc = locfile ;startinfo = yes ;gammucoding...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060322/b3ddf5ba/attachment-0001.pgp