Another aye from here.<br><br>David.<br><br><br><div class="gmail_quote">On Tue, Apr 29, 2008 at 8:30 AM, Shachar Shemesh <<a href="mailto:shachar@shemesh.biz">shachar@shemesh.biz</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Abstract:<br>
With a bit of manual reading, anyone can learn how to create a program<br>
that has more than one thread of execution. This breaks down, very<br>
rapidly, however, as the inter-dependencies inside the program start to<br>
burden you down, to the point where you get race bugs that are close to<br>
impossible to find. Fixing those typically involve using the various<br>
locking mechanisms. The result is, more often than not, a program that<br>
both works much slower than the number of threads and processors would<br>
suggest it should, AND at the same time still has race conditions.<br>
<br>
This lecture will try to give rules relating to how to construct your<br>
program to begin with so that it will provide high performance, be<br>
maintainable (for some definition of maintainable), and be bug<br>
efficient. In other words, this lecture is about learning to think<br>
"multi-threaded". In fact, efficient enough multi-threaded design do not<br>
even need to have more than one thread of execution......<br>
<br>
All in favor say "aye".<br>
<br>
Shachar<br>
_______________________________________________<br>
Haifux mailing list<br>
<a href="mailto:Haifux@haifux.org">Haifux@haifux.org</a><br>
<a href="http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux" target="_blank">http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux</a><br>
</blockquote></div><br>