Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: anton@mips.complang.tuwien.ac.at (Anton Ertl) Newsgroups: comp.arch Subject: Re: Threads (was Re: MSI interrupts) Date: Wed, 02 Apr 2025 06:25:56 GMT Organization: Institut fuer Computersprachen, Technische Universitaet Wien Lines: 15 Message-ID: <2025Apr2.082556@mips.complang.tuwien.ac.at> References: <0FTGP.567700$f81.368330@fx48.iad> Injection-Date: Wed, 02 Apr 2025 08:28:31 +0200 (CEST) Injection-Info: dont-email.me; posting-host="cc4b37c4dcc6d052c22f45fb6c696c8a"; logging-data="1143805"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+g/vMomnLfMlg2ehZfRTb3" Cancel-Lock: sha1:mj/Vs1mbrb/4ir0DPIm/8avmwaw= X-newsreader: xrn 10.11 Bytes: 1765 scott@slp53.sl.home (Scott Lurndal) writes: >Unix SVR4ES/MP actually had >both kernel threads (called lightweight processes (LWP)) and user-level >threads in an M-N setup (M user threads multiplexed on N kernel threads). > >Didn't turn out to be particularly useful. Maybe the SVR4ES/MP stuff was not particularly useful. Combining user-level threads and kernel threads in an M-N setup has turned out to be very useful in, e.g., Erlang applications. - anton -- 'Anyone trying for "industrial quality" ISA should avoid undefined behavior.' Mitch Alsup,