<div dir="ltr">It seems to me that each student drinknig process really needs a specific core of resources, but there is no reason you should all be sharing the same core. Why not assign each student a unique core specifically designed for optimal drinking efficiency? I should think a keg fashioned into a chair and a hose would do nicely. Each student drinking process would only have to access the Genevieve once when the process is called, and once again to close out the tab when the process is complete. Naturally, Genevieve's efficiency would still come into play if two processes began or ended at the same time, but it's not my fault you're still running Windows ME. <br>
<br>In conclusion, drinking beer is a highly parallizable process. It would run faster on a GPU. <br><br>Jesse, whois drinking the Kool-Aid.<br>
<br><div class="gmail_quote">On Wed, Sep 24, 2008 at 12:22 PM, Boris Lipchin <span dir="ltr"><<a href="mailto:blipchin@ece.cmu.edu" target="_blank">blipchin@ece.cmu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As I sit here in Operating Systems lecture, I have started to question<br>
some inner-workings of the Universe. Here are some examples of the<br>
fruits of a single OS lecture.<br>
<br>
Does sleep truly exist? Do the OS TAs have souls? How long has Eckerd<br>
been growing his beard? Will my kernel ever trully attain Zen?<br>
<br>
The most fundamental question however, is that of the Drinking ECE<br>
Majors. How do a bunch of ECE majors manage hotly demanded resources<br>
such as beer and cups in the highly preemptable environment that is phi<br>
bar? Although you may not know it, we have been drinking at Phi Bar<br>
completely unaware of race conditions running rampant at the table.<br>
Problems such as deadlock (oh ... you're going to finish it?), livelock<br>
(no no, after you), lack of beer/resources (crap!) , and worst of all<br>
starvation (where's my beer?!!) have made our beer drinking woefully<br>
inefficient.<br>
<br>
No more.<br>
<br>
From now on we will implement cutting edge synchronization algorithms<br>
to optimize consumption of Phi Bar's precious resources. Today at Phi<br>
Bar we will experiment with several synchronization and scheduling<br>
methodologies, so please come prepared to drink triple portions while<br>
taking careful timing measurements of beer consumption.<br>
<br>
Feel free to email the list with any ideas of how we can improve our system.<br>
<br>
Boris<br>
_______________________________________________<br>
Ece-phi mailing list<br>
<a href="mailto:Ece-phi@lists.andrew.cmu.edu" target="_blank">Ece-phi@lists.andrew.cmu.edu</a><br>
<a href="https://lists.andrew.cmu.edu/mailman/listinfo/ece-phi" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/ece-phi</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Jesse Guss<br>201 W Ferndale Ave.<br>Sunnyvale CA 94085<br>412-519-8275<br>
</div>