Correct me if I'm wrong, but since hard drives can't read from two places at once are speed increases actually realized from trying to multithread reads with TagLib?<br><br><div class="gmail_quote">2011/3/5 Lukáš Lalinský <span dir="ltr"><<a href="mailto:lalinsky@gmail.com">lalinsky@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Mar 5, 2011 at 6:00 PM, Stephen F. Booth <<a href="mailto:me@sbooth.org">me@sbooth.org</a>> wrote:<br>
> I've also run into crashes like this in the past, when I tried to realize<br>
> speed increases by parsing several files simultaneously in separate threads.<br>
> It seems that if atomic increment/decrement were added to RefCounter, as<br>
> long as a single file wasn't shared across threads then STL thread safety<br>
> wouldn't be an issue. I'm not sure which statics could affect this, as I<br>
> haven't looked through the code in a while. Is thread safety (or some level<br>
> of it) something planned for a future release?<br>
<br>
</div>I don't think thread-safe TagLib is a particularly good idea. It would<br>
cause too many speed penalties for no good reason. I definitely want<br>
to be able to call different instances of TagLib classes from<br>
different threads though. I believe that fixing the RefCounter should<br>
be the only thing that is needed. The other static instances are<br>
read-only, as far as I remember.<br>
<div><div></div><div class="h5"><br>
Lukas<br>
_______________________________________________<br>
taglib-devel mailing list<br>
<a href="mailto:taglib-devel@kde.org">taglib-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/taglib-devel" target="_blank">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br>
</div></div></blockquote></div><br>