From owner-freebsd-hackers Sun Feb 6 20:52:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (h24-67-218-186.xx.wave.shaw.ca [24.67.218.186]) by builder.freebsd.org (Postfix) with ESMTP id C3FA23E2C for ; Sun, 6 Feb 2000 20:52:15 -0800 (PST) Received: from io.yi.org (jake@localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (8.9.3/8.9.3) with ESMTP id UAA46328; Sun, 6 Feb 2000 20:53:34 -0800 (PST) (envelope-from jake@io.yi.org) Message-Id: <200002070453.UAA46328@io.yi.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG, arla-drinkers@stacken.kth.se Subject: Re: Writing a multithreaded daemon process In-reply-to: Your message of "Sun, 06 Feb 2000 14:46:31 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Feb 2000 20:53:33 -0800 From: Jake Burkholder Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the daemon can somehow reside entirely inside the kernel, like NFS > daemon, we can save those crossings. But the daemon is a multi-threaded > process and we have no kernel thread yet, so I do not know how to do > better if possible. Maybe all user filesystems have to live with this > limitation. There's kernel threads and then there's kernel threads. kthread_create (see sys/kern/kern_kthread.c) will create a new process which shares it's address space with the kernel; that might be what you want. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message