Subj : Re: Paper - User-Level Threads for Hierarchically Composed Simulations To : comp.programming.threads From : Mark Hodson Date : Sun Aug 21 2005 01:20 pm Most probably the only reason it was google resistant at the time was I'd created the page on which the paper resided literally hours before posting this article, so it wasn't in google's database to begin with. I have since submitted the page to be googlebotted. Given the use of "pthread_" prefix for all POSIX thread operations, it only seemed logical to use "uthread_" prefix for my API, with very similar semantics on the use of functions, parameters, etc. So "uthreads" stays. ;) Expected some "interesting, where can we get the src" comments, but not so? David Hopwood wrote: > Mark Hodson wrote: > >> G'day to the comp.programming.threads crew, >> >> Quite some months ago I quizzed this newsgroup, and got some quite >> reasonable feedback to some user-level threading general questions. >> >> At the time I was investigating user-level threading from the point of >> view of supporting a novel simulation architecture. Simulation >> architectures like web-servers are probably one of the few areas where >> specialised use of user-level threading can make a pretty significant >> difference and where there's enough specialisation to put clamps on >> what any sort of user-level threading library actually needs to do! >> >> Anyway, FYI the paper was published at a simulation conference so you >> can read it at. >> >> http://members.ozemail.com.au/~mjhodson/papers/papers.html > > > There are several threading libraries sometimes called uthread[s]: > > - FreeBSD's standard thread library written by John Birrel > - Stackless Python's microthreads library > (http://willware.net:8080/uthread.html) > - one for C using setjmp/longjmp > (http://www.bridgeport.edu/sed/projects/cs597/spring2005/srinivas/uthrds_impl_web.pdf); > > - a thread library for the Psyche OS > - a thread library for distributed memory systems > (http://citeseer.ist.psu.edu/98163.html) > - AIX and Digital Unix (or whatever it's called now) also use structures > called uthread > > As a result the term "uthread" is completely Google-resistant, and I was > unable to find the library referred to in the paper (even by Googling > "uthread Mark Hodson"). Can I suggest using a more distinctive name? > .