Date: Wed, 24 Nov 1999 20:19:54 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Chuck Robey <chuckr@picnic.mat.net> Cc: Daniel Eischen <eischen@vigrid.com>, Julian Elischer <julian@whistle.com>, Nate Williams <nate@mt.sri.com>, freebsd-arch@freebsd.org, jasone@freebsd.org Subject: Re: Threads Message-ID: <383BC9D9.B7E721C9@newsguy.com> References: <Pine.BSF.4.10.9911240001580.20163-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey wrote: > > OK, then let me ask another question: are we at all concerned about maybe > following an already established thread API, or are we going to create our > own? Things like user threads probably could work as then are now (albeit > perhaps with only minor changes in performance) and stuff with runtimes > like Java wouldn't care, but big programs like XFree86 and Netscape, and > specially made daemons trying to do things like mass factoring, > that are going to really want to manipulate real concurrency levels, > they're going to have to be aware of our real underlying API, so making a > unique one will complicate a lot of lives. But do they? Do Netscape, XFree86 or any other program you know of make use of underlying APIs instead of lib-exported, POSIX-compliant APIs? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Then again maybe not going to heaven would be a blessing. Relkin liked a certain amount of peace and harmony, since there'd been a pronounced shortage of them in his own life; however, nothing but peace and harmony, forever and forever? He wasn't sure about that. And no beer? Very dubious proposition." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?383BC9D9.B7E721C9>