Date: Sun, 27 Jun 1999 23:34:22 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Warner Losh <imp@harmony.village.org> Cc: hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via newconfig Message-ID: <Pine.BSF.3.95.990627233124.8298O-100000@current1.whistle.com> In-Reply-To: <199906280609.AAA13467@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
please yes.. eventually we'll be using it to fire off a thread for every interrupt source if we go the BSDI way. (as dicussed with various people at USENIX) I was actually thinking about this today... now this is threads within the kernel, and not kernel support for user threads right? julian On Mon, 28 Jun 1999, Warner Losh wrote: > > I'd like to bring a kernel thread implementation, ported from NetBDS > by the newconfig project, into the kernel. Who would like to review > things before they go into the tree? I can see many benefits for > having this in the tree, but very little downside. This should allow > people to more easily port raid-frame from NetBSD if they desire. > > FYI, this is an outshoot of the porting of the newconfig code to > new-bus. Each bridge controller has its own even thread to handle > cards events in a sane manner. It is basically a stripped down > pccardd in the kernel, but one that has a huge hint database. I'm not > proposing, at this time, to bring it on. I just want to get the > kthread stuff in as a separate issue. > > Comments? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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.3.95.990627233124.8298O-100000>