Date: Sat, 24 Feb 2007 13:47:43 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: Martin Blapp <mb@imp.ch> Cc: rob@debank.tv, freebsd-threads@freebsd.org Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so Message-ID: <Pine.GSO.4.64.0702241344240.6160@sea.ntplx.net> In-Reply-To: <20070224185741.F18301@godot.imp.ch> References: <20070220153632.E4139@godot.imp.ch> <Pine.GSO.4.64.0702201138080.12034@sea.ntplx.net> <20070220174221.B4139@godot.imp.ch> <Pine.GSO.4.64.0702201145420.12034@sea.ntplx.net> <20070220190347.C4139@godot.imp.ch> <Pine.GSO.4.64.0702201319230.12034@sea.ntplx.net> <20070220225303.V4139@godot.imp.ch> <Pine.GSO.4.64.0702201724590.12034@sea.ntplx.net> <20070220234734.H4139@godot.imp.ch> <20070221000830.V4139@godot.imp.ch> <20070221020335.Y4139@godot.imp.ch> <20070224103422.V18301@godot.imp.ch> <Pine.GSO.4.64.0702241012230.5266@sea.ntplx.net> <20070224185741.F18301@godot.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Feb 2007, Martin Blapp wrote: > > 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 ? I don't know... > 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 ? Yes, fix clamd so it doesn't fork() without doing an exec(). POSIX says that behavior is undefined when threaded applications fork() and call non-async-signal-safe functions. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0702241344240.6160>