Date: Sun, 20 Feb 2005 17:40:28 +0300 From: Dmitry Agaphonov <rzhe@agava.com> To: freebsd-hackers@freebsd.org Subject: Re: kqueue & pthread Message-ID: <20050220174028.6efc483d.rzhe@agava.com> In-Reply-To: <20050209155136.GC65523@green.homeunix.org> References: <20050209173625.29d50ffd.rzhe@agava.com> <20050209144924.GB65523@green.homeunix.org> <20050209183952.30f4c5b6.rzhe@agava.com> <20050209155136.GC65523@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 9 Feb 2005 10:51:36 -0500
Brian Fundakowski Feldman <green@freebsd.org> wrote:
BFF> The LinuxThreads library seems to be the best-supported way. I don't think
BFF> that there should be legal/licensing issues using it.
Unfortunatelly, I can't use the LinuxThreads library, it simply does not
compile on FreeBSD 4.10 (and I assume that on latest 4.x too) with
gcc-3.4.4. Errors appear when it's building code from /usr/src tree with
the newer compiler.
FreeBSD 4.x is a mandatory target platform and using gcc-3.4 is a strong
wish. So, I'm going to have kernel threads via rfork_thread(3) and the
main question I stuck on is which libc functions I need to wrap to make
them thread-safe and reentrant on multiprocessor systems, since
rfork_thread(3)s are created with RFMEM flag and libc_r is not used.
Could one give ideas or point where to read?
Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050220174028.6efc483d.rzhe>