View Single Post
Old 11-04-2014, 08:59 PM   #60
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,503
Karma: 28548962
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Quote:
Originally Posted by ShellShock View Post
Or it could be a thread-safety problem. I don't know if send to device is single threaded or not; if not, then the bug could be due to lack of synchronisation across threads.
The device driver system in calibre is single threaded -- all device driver entry points are called on the same, dedicated thread. There are a few minor exceptions to this, which are documented in devices/interface.py, just search for thread.

Individual drivers are free to use multiple threads internally if they like.
kovidgoyal is online now   Reply With Quote