Date: Thu, 3 Mar 2005 14:14:30 +0530 From: "Andriy Tkachuk" <andrit@ukr.net> To: <threads@freebsd.org> Subject: Re: patch for threads/76690 - critical - fork hang in child for-lc_r Message-ID: <010b01c51fcd$3d0dabb0$090210ac@BORJA> References: <Pine.GSO.4.43.0503021042310.26125-100000@sea.ntplx.net> <000b01c51fbb$4189ea30$090210ac@BORJA> <005201c51fc2$d8676b60$090210ac@BORJA> <4226C7B6.4060901@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
actually, this test prog was written after there were problems with multithreaded domestic application server, that was tested under load. this one is using intensively hash manipulations. it is develped for redhat 7.3 and tested there. it was interesting for me, how it will behaves on fbsd in linux emulation - it was fine (note: there is linix pthreads). then we wrote this test prog to investigate the threads with heap manipulations sumultaneousely. It was interesting for me to investigate the same in freebsd. that's how it was. :) > Hmm, libc_r and libpthread handle spinlock differently which malloc > uses to protect itself, some real world benchmarks are better than this. > > David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010b01c51fcd$3d0dabb0$090210ac>