Date: Wed, 9 Jul 2003 18:49:25 +0200 From: "Kai Mosebach" <kai.mosebach@freshx.de> To: <deischen@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: AW: LinuxThreads replacement Message-ID: <001b01c3463a$0f907a00$0100a8c0@alpha> In-Reply-To: <Pine.GSO.4.10.10307091234350.3409-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Currently, im porting the SapDB (www.sapdb.org) to FreeBSD (www.komadev.de/sapdb), which makes heavy use of the lthreads, but 1.) isnt running stable on 5.1 (not sure whether its a lthreads problem) 2.) is not the fastest (i guess) 3.) has more (especially memory) overhead for example, for on database instance, there are about 80 (lthread) processes hanging around. So i thought of a simple complete recompiling. Would you more likely use libthr or libkse,=20 as kse is not complete yet, isnt it ? regards -----Urspr=FCngliche Nachricht----- Von: Daniel Eischen [mailto:eischen@vigrid.com]=20 Gesendet: Mittwoch, 9. Juli 2003 18:42 An: Kai Mosebach Cc: freebsd-threads@freebsd.org Betreff: Re: LinuxThreads replacement On Wed, 9 Jul 2003, Kai Mosebach wrote: > Hi, >=20 > can libthr / libkse easily be used as a liblthreads (LinuxThreads) > replacement ? I would doubt that you'd be able to copy (or use libmap.conf) libthr/libkse over liblthreads. I suspect that the mutex types (and perhaps others) may be implemented differently so that their sizes are incompatible. For instance, if linuxthreads defines pthread_mutex_t as a struct, that wouldn't work when FreeBSD defines them to be pointers to structs. Actually, maybe that would work since the FreeBSD types are not greater in size. But there are other possible problems -- pthread_cleanup_push() implemented as macros in linuxthreads for one. On the other hand, if you want to recompile something that currently uses linuxthreads, it should work using one of our thread libraries. --=20 Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001b01c3463a$0f907a00$0100a8c0>