Date: Sat, 20 Nov 1999 19:32:22 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Jason Evans <jasone@canonware.com> Cc: David Greenman <dg@root.com>, Nate Williams <nate@mt.sri.com>, freebsd-arch@freebsd.org Subject: Re: Core responsibilities [was Re: PHK: "Shut up and go away quietly"] Message-ID: <Pine.BSF.4.10.9911201927410.6767-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.4.10.9911201915280.6767-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I gotta learn to type..
On Sat, 20 Nov 1999, Julian Elischer wrote:
> I wonder if we can try a new development scheme?
> You have amandate to do almost anythign to make threads work..
a mandate ng
> there are a lot of people who would like to help you work on this..
> Even a full time job doesn't give enough time for doing this all on your
> own completely in isolation.
>
> How about if you coem on as "main threads guy and thread team leader"?
come
> Take over the discussion lead, and I know I'd be willing to take on
> specific tasks.. e.g. "split the proc struct into proc and thread parts"
> "get us a new call-gate for the threaded syscalls" "make a skelaton in the
skeleton
> sources to compile a version of libc-R using the new callgate"
>
> "Fix PS to show all threads and not just the main one"
> "fix /proc for the new world"
> etc.etc.
>
> there are lots of people who know how to do these bits
> And tehy will hapily do these thongs and feed you back patches
they happily things
> if you can use you new 'Thread-czar' position to organise it.
>
> Julian
>
Of course the first thing we ned to do is get on with the basic design.
As we do so somethings will become obviously needed..
e.g I'm thinking of trying to do the proc/thread bit tonight
just for fun. (of course ps will barf :-)
>
>
> On Sat, 20 Nov 1999, Jason Evans wrote:
>
> > On Sat, Nov 20, 1999 at 04:11:19PM -0800, Julian Elischer wrote:
> > > On Sat, 20 Nov 1999, David Greenman wrote:
> > >
> > > > >What are we going to do with kernel threads? None of the core members
> > > > >have yet to respond?.
> > > >
> > > > Walnut Creek CDROM just hired Jason Evans to work on it.
> > >
> > > Since we've been having a threads "what do we do next" discussion on -arch
> > > (or trying) doesn't it seem like a good idea that someone would MENTION
> > > this fact to us? Especially as we have a design partly thrashed out in
> > > our minds and have started experimenting with ideas!
> >
> > I start at Walnut Creek on Monday, and had every intention of making that
> > known on Monday. As for Jordan's announcement, I somehow missed it too. =)
> >
> > > Is there any small chance that Jason Evans will take part in and not just
> > > over-ride the work that has already been going on?
> >
> > As for the threads discussion on -arch, I've been following the discussion
> > *very* closely. No, I won't over-ride what has happened so far; I am in
> > total agreement with almost all of the points that have been hashed out
> > thus far. Walnut Creek CDROM's (and my) motivation is simply to have
> > someone who can concentrate full time on moving threads forward in
> > FreeBSD.
> >
> > Jason
> >
> > Jason Evans <jasone@canonware.com>
> > http://www.canonware.com/~jasone
> > Home phone: (650) 856-8204
> > "I once knew a happy medium. Her name was Zohar." - James Foster
> >
> >
>
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-arch" in the body of the message
>
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.9911201927410.6767-100000>