From owner-cvs-all@FreeBSD.ORG Fri Sep 24 21:34:24 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CA4916A4CE; Fri, 24 Sep 2004 21:34:24 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBC4443D3F; Fri, 24 Sep 2004 21:34:23 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C4B8F7A41E; Fri, 24 Sep 2004 14:34:22 -0700 (PDT) Message-ID: <415492DE.4070801@elischer.org> Date: Fri, 24 Sep 2004 14:34:22 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: John Baldwin References: <200409241958.i8OJwm8Y051147@repoman.freebsd.org> <200409241633.06963.jhb@FreeBSD.org> In-Reply-To: <200409241633.06963.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Joerg Wunsch Subject: Re: cvs commit: src/share/man/man9 kthread.9 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 21:34:24 -0000 John Baldwin wrote: >On Friday 24 September 2004 03:58 pm, Joerg Wunsch wrote: > > >>joerg 2004-09-24 19:58:47 UTC >> >> FreeBSD src repository >> >> Modified files: >> share/man/man9 kthread.9 >> Log: >> Document that kthread_exit()ing will cause a wakeup(9) on the thread >> handle. >> >> MFC after: 1 week >> >> > >It's not the thread handle, it's the proc pointer: > > /* > * If this is a kthread, then wakeup anyone waiting for it to exit. > */ > if (p->p_flag & P_KTHREAD) > could be an idea to use something thread specific as it is possible that kernel therads may some day become actual threads in one "kernel" process. The things that stop this at the moment include that there is no p_comm field in a thread so 'ps' would ahve nothing to show to identify what the threads were.. I have been considerring adding a td_desc field to threads to be used in teh same way... > > >