From owner-freebsd-arch Thu Nov 22 22:14:48 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E773E37B417; Thu, 22 Nov 2001 22:14:45 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAN6Eia83150; Thu, 22 Nov 2001 23:14:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAN6Ei722956; Thu, 22 Nov 2001 23:14:44 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111230614.fAN6Ei722956@harmony.village.org> To: Julian Elischer Subject: Re: Kernel Thread scheduler Cc: Mike Smith , John Baldwin , Steve Kargl , arch@FreeBSD.ORG In-reply-to: Your message of "Thu, 22 Nov 2001 13:58:08 PST." References: Date: Thu, 22 Nov 2001 23:14:44 -0700 From: Warner Losh 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 In message Julian Elischer writes: : This is a valid point.. should I change the name in the next round a bit? : and if so what to? I don't really want "k_thread", any more than I would : think of changing proc to k_proc.. Theoretically a user program shouldn't : even know about proc and thread.. what is there in proc.h that a : user program needs? Well, there's always a typedef hack :-) /me ducks behind d_thread_t Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message