Date: Sun, 12 Oct 1997 22:37:47 -0700 (PDT) From: svincent <svincent@scf-fs.usc.edu> To: freebsd-bugs@freebsd.org Message-ID: <Pine.SV4.3.94.971012223731.2185A-120000@aludra.usc.edu>
next in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --WAA20810.876719914/aludra.usc.edu Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <Pine.SV4.3.94.971012223731.2185C@aludra.usc.edu> --WAA20810.876719914/aludra.usc.edu Content-Type: MESSAGE/DELIVERY-STATUS Content-ID: <Pine.SV4.3.94.971012223731.2185D@aludra.usc.edu> Content-Description: Reporting-MTA: dns; aludra.usc.edu Arrival-Date: Sun, 12 Oct 1997 22:18:31 -0700 (PDT) Final-Recipient: RFC822; freebsd-problems@freebsd.org Action: failed Status: 5.1.1 Remote-MTA: DNS; hub.freebsd.org Diagnostic-Code: SMTP; 550 <freebsd-problems@freebsd.org>... User unknown Last-Attempt-Date: Sun, 12 Oct 1997 22:18:33 -0700 (PDT) --WAA20810.876719914/aludra.usc.edu Content-Type: MESSAGE/RFC822 Content-ID: <Pine.SV4.3.94.971012223731.2185E@aludra.usc.edu> Content-Description: Return-Path: <svincent@aludra.usc.edu> Received: from localhost (svincent@localhost) by aludra.usc.edu (8.8.4/8.8.4/usc) with SMTP id WAA20808; Sun, 12 Oct 1997 22:18:31 -0700 (PDT) Date: Sun, 12 Oct 1997 22:18:31 -0700 (PDT) From: svincent <svincent@aludra.usc.edu> To: freebsd-smp@freebsd.org cc: freebsd-problems@freebsd.org Subject: 3.0-971010-SNAP ? In-Reply-To: <Pine.SV4.3.94.971012174147.21287A-100000@aludra.usc.edu> Message-ID: <Pine.SV4.3.94.971012221626.19060B-100000@aludra.usc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've tried installing this, but it seems to only come up with the 2.2.5-BETA release. The 3.0-971010-SNAP directory seems to be containing 2.2.5-BETA stuff. The 3.0-971012-SNAP directory in not available to cd to. What's up ? Vince On Sun, 12 Oct 1997, svincent wrote: > > Hello, > > Pavlin Radoslavov and I (S Vincent) are graduate students at USC, LA. > We have a distributed systems project to do, and were serious and eager > to do some coding for a multiprocessor system. > > We looked at the to-do list and were interested in these two things. > > Additional run queue management. > > * run queue needs restructuring so that there is a per-cpu queue of > runnable tasks. This means that a cpu could access it's own run > queue outside the kernel lock. > > * make shared address spaces work.. The VM system needs to know when > the page tables of a "!= curproc" process might be in use on > another cpu (ie: check all other SMPcurproc[]'s). When modifying > the current process it needs to check the vmspace reference count > and do the appropriate IPI's to the other cpu. Locking is a problem > here. > > We'd be grateful to have any advice - while we get done with > installing, tests and such things. > > S Vincent > Pavlin Radoslavov > > > --WAA20810.876719914/aludra.usc.edu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.94.971012223731.2185A-120000>