From owner-freebsd-current Tue Jul 24 16: 0:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C297C37B405; Tue, 24 Jul 2001 15:59:57 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA19999; Mon, 23 Jul 2001 22:54:18 -0700 (PDT) Message-ID: <3B5CEF48.B09A700B@elischer.org> Date: Mon, 23 Jul 2001 20:45:12 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: Progress report: KSEs. References: <3B5BD579.400FE65E@elischer.org> <20010723151258.A52202@dragon.nuxi.com> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Mon, Jul 23, 2001 at 12:42:49AM -0700, Julian Elischer wrote: > > step 1: get proc structure broken up, with system still running: done (twice) > > Can you post your diff to the proc structure? > > ... > > > -random_ioctl(dev_t dev, u_long cmd, caddr_t addr, int flags, struct proc *p) > > +random_ioctl(dev_t dev, u_long cmd, caddr_t addr, int flags, struct thread *td) > > This implies `struct thread' has replaced `struct proc'. (I could be > wrong, but cannot be sure until you post the `struct proc' and related > structure changes/additions) A thread is blockable and anything that might block (e.g. a syscall,( e.g. ioctl)) needs to talk in terms of the thread rather than the process. so, yes, maybe > 50% of uses of "struct proc *p" get changed to "struct thread *td". The proc structure however still exists. > There is no `struct thread' in Jason's KSE paper. > Why aren't you > following the paper > http://people.freebsd.org/~jasone/refs/freebsd_kse/freebsd_kse.html? Well since I made up the terminology in the paper,... because I changed my mind about it? My original posts said.. "lets call these KSEs etc. tillwe are completely sure what they do and can give them better names. The basic unit turns out to be the thread which can be blocked so calling it a KSEC is plain confusing. As you requested, I include my current version of proc.h at http://www.freebsd.org/~julian this is NOT the version that ran under step #1 but rather as it looks now, half way through step #2. > > -- > -- David (obrien@FreeBSD.org) -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message