From owner-freebsd-current Tue Nov 26 23:45:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FCED37B401 for ; Tue, 26 Nov 2002 23:45:11 -0800 (PST) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA3B243EA9 for ; Tue, 26 Nov 2002 23:45:10 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc02.attbi.com (sccrmhc02) with ESMTP id <2002112707450900200sobf2e>; Wed, 27 Nov 2002 07:45:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA57750; Tue, 26 Nov 2002 23:42:18 -0800 (PST) Message-Id: <200211270742.XAA57750@InterJet.elischer.org> Date: Tue, 26 Nov 2002 23:42:17 -0800 (PST) From: Julian Elischer To: Terry Lambert Cc: Nate Lawson , current@FreeBSD.ORG Subject: Re: [PATCH] Searching for users of netncp and nwfs to help 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 debug5.0problems In-Reply-To: <3DE46776.27DF0FD@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 26 Nov 2002, Terry Lambert wrote: > Julian Elischer wrote: > > > The answer is that "the code doesn't care what thread"; it would > > > prefer to not have to think in terms of threads at all, but if > > > you want to force it to, then it's going to think in terms of > > > "blocking contexts for the benefit of FreeBSD code it calls", > > > and nothing else. > > > > Hense the confusion as to whether to use a thread or a proc.. > > Not confusing at all. The only issue is references to the > connection structure caches proc, which uses the first thread > on the cached proc; otherwise, it uses the thread that was > passed in. Where does the passed in thread come from? Generally don't use a thread pointer other than yourself unless you have a lock on the proc structure, or the schedlock. Certainly never store it anywhere.. Particularly anywhere that may persist while you sleep in any way. -exception.. kernel threads- .. they are persistant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message