From owner-freebsd-current@FreeBSD.ORG  Sun Jan 22 14:21:19 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
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 3E45F16A41F
	for <current@freebsd.org>; Sun, 22 Jan 2006 14:21:19 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D004043D46
	for <current@freebsd.org>; Sun, 22 Jan 2006 14:21:13 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k0MEL5Ns011087; 
	Sun, 22 Jan 2006 09:21:05 -0500 (EST)
Date: Sun, 22 Jan 2006 09:21:05 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20060121.234404.95801924.imp@bsdimp.com>
Message-ID: <Pine.GSO.4.43.0601220909360.11194-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
Cc: current@freebsd.org
Subject: Re: kernel thread as real threads..
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2006 14:21:19 -0000

On Sat, 21 Jan 2006, M. Warner Losh wrote:

> In message: <Pine.GSO.4.43.0601201443570.1773-100000@sea.ntplx.net>
>             Daniel Eischen <deischen@freebsd.org> writes:
> : On Fri, 20 Jan 2006, Scott Long wrote:
> : >
> : > Does pthreads allow the programmer to name threads in a user and/or
> : > kernel visible way?  Is this something that is really all that
> : > important?
> :
> : Only in a non-portable way.  See pthread_set_name_np(3).
>
> This 'non-portable' way is in heavy use in at least one user of
> FreeBSD's software base.

Well, I'm not advocating its removal, just clarifying that
there is no POSIX interface for setting a thread's name.
I originally added that interface as a debugging aid for
application developers after finding it useful myself in
debugging the library.  I'm not sure you want to reuse the
same interface for setting kernel thread names.  For KSE
or libc_r type threads, it wouldn't work too well.

-- 
DE