From owner-freebsd-arch Sat Dec 16 8:53:20 2000 From owner-freebsd-arch@FreeBSD.ORG Sat Dec 16 08:53:19 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C9FE737B400; Sat, 16 Dec 2000 08:53:16 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA26605; Sun, 17 Dec 2000 03:53:13 +1100 Date: Sun, 17 Dec 2000 03:53:12 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: arch@FreeBSD.ORG Subject: Re: kthread API In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Dec 2000, John Baldwin wrote: > I'd like to make some of the kernel API's a little more consistent as far as in > their naming. The first one I'd like to tackle is the kthread API. > Specifically, I'd like to stick the whole API under a kthread_* API. This > would result in the following: > > Old Name New Name > -------- -------- > kproc_start kproc_start > shutdown_kproc kproc_shutdown > kthread_create kthread_create > kthread_exit kthread_exit > resume_kproc kthread_resume > suspend_kproc kthread_suspend > kproc_suspend_loop kthread_suspend_check "kthread" is a silly abbreviation, like "vmemory" would be for "virtual memory". Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message