Date: Wed, 8 Dec 1999 16:44:50 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: "Daniel M. Eischen" <eischen@vigrid.com> Cc: freebsd-arch@freebsd.org Subject: Re: Threads discussion Message-ID: <Pine.BSF.4.10.9912081636000.23315-100000@current1.whistle.com> In-Reply-To: <384EF8CB.D83F47EB@vigrid.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 8 Dec 1999, Daniel M. Eischen wrote: > Julian Elischer wrote: > > > > is not dead.. we're all catching our breath! > > > > Tomorrow at the Bay Area Freebsd Users Group (BAFUG) > > there will be a food fight over threads kernel support. > > Anyone within driving range is urged to attend. > > Hey, this isn't fair! :-) just chance.. Alfred perlstein will be there too. > > > I'll be there, as will Matt, Terry, and Jason. > > If I wasn't 2700 miles away, I'd be there too. Please > let us know what was discussed. I think we'll just be swapping ideas. but we MAY be able to get the speaker phone hooked in.. wouldn't that be interesting? I'm not sure how I'd get a conference call set up but that may even be a possibility. (!) > > BTW, I don't think the kernel can always know if a subprocess > is in a notification upcall by looking at the user stack > pointer. The upcall notification may be temporarily switched > to resume a preempted thread holding a critical resource. I wasn't thinking of just upcalls but it may be important to know whether it is in the scheduler when responding to a pagefault. I think page faults in the scheduler should just block. > > Dan Eischen > eischen@vigrid.com > 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?Pine.BSF.4.10.9912081636000.23315-100000>