From owner-freebsd-arch Wed Nov 7 17: 9:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9F3D637B418 for ; Wed, 7 Nov 2001 17:09:16 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fA8194B52286; Wed, 7 Nov 2001 20:09:04 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Nov 2001 20:09:04 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer Cc: freebsd-arch@FreeBSD.org Subject: Re: Changing req->p to req->td in sysctl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 7 Nov 2001, Julian Elischer wrote: > On Wed, 7 Nov 2001, Robert Watson wrote: > > > I should mention that both GENERIC and LINT build fine, but that I wasn't > > sure what to do about the use of req->p in netsmb/netncp. Both appear > > still to use pre-KSE struct proc all over the place, altough the .h files > > have been updated (?). I'd be happy to try to update them to post-KSE, > > although I don't use either so can't test them. > > netsmb and netncp, along with smbfs and nwfs are the two modules that > defeated me in trying to change them to a threaded model. This is > because they have some idea of a "session" but it is not clear to me > that whether a session is a "per thread or Per process" thing. Hmm. Well, I'll go ahead and commit my patch as is, and push the thread pointers down into if_ioctl, which will let me expunge a number of curproc references (and continue moving us towards td_ucred). If time permits, I'll look some more at the ncp/smb code, but given its complexity, I'm not sure how much progress I can make. So if someone wants to pick up on this, that would be great--we certainly don't want to let these fall by the wayside for much longer. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message