From owner-freebsd-threads@FreeBSD.ORG Sat Feb 24 18:06:36 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2C9216A405; Sat, 24 Feb 2007 18:06:36 +0000 (UTC) (envelope-from mb@imp.ch) Received: from pop.imp.ch (mx2.imp.ch [157.161.9.17]) by mx1.freebsd.org (Postfix) with ESMTP id 7D38113C4A3; Sat, 24 Feb 2007 18:06:36 +0000 (UTC) (envelope-from mb@imp.ch) Received: from dan.imp.ch (godot.imp.ch [157.161.4.8]) by pop.imp.ch (8.13.8/8.13.8/Submit_imp) with ESMTP id l1OI6WBb011459; Sat, 24 Feb 2007 19:06:33 +0100 (CET) (envelope-from mb@imp.ch) Date: Sat, 24 Feb 2007 19:06:32 +0100 (CET) From: Martin Blapp To: Daniel Eischen In-Reply-To: Message-ID: <20070224185741.F18301@godot.imp.ch> References: <20070220153632.E4139@godot.imp.ch> <20070220174221.B4139@godot.imp.ch> <20070220190347.C4139@godot.imp.ch> <20070220225303.V4139@godot.imp.ch> <20070220234734.H4139@godot.imp.ch> <20070221000830.V4139@godot.imp.ch> <20070221020335.Y4139@godot.imp.ch> <20070224103422.V18301@godot.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: rob@debank.tv, freebsd-threads@freebsd.org Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2007 18:06:37 -0000 Hi, >> Running ktrace with libc_r or libthr I can't see a single call to fork(). >> Is ktrace lying to me ? Why do I only see fork()s with libpthread ? > > The kse upcalls might look like forks to ktrace? > That could be. Is it easy to fix this for ktrace ? Anyway, that still doesn't solve the problem for me, since clamd with libpthreads is extremly CPU hungry and is slow. I really miss something to profile like strace on solaris to see where it spends most CPU cycles. The problem is not that it doesn't work, the problem is that it works far too slow. Do you have any ideas ? Martin