Date: Sat, 13 Dec 2003 02:18:53 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Christopher Sedore <cmsedore@maxwell.syr.edu> Cc: threads@freebsd.org Subject: RE: KSE system scope vs non system scope threads Message-ID: <Pine.GSO.4.10.10312130217220.29477-100000@pcnet5.pcnet.com> In-Reply-To: <20031212184457.S47162-100000@qwerty.maxwell.syr.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Dec 2003, Christopher Sedore wrote: > > On Mon, 8 Dec 2003, Daniel Eischen wrote: > > > > > Are you using gethostby* or anything else in libc that isn't > > thread-safe without using mutexes to protect them? > > I had a couple stray uses of strtok left over from an earlier non-threaded > version--I cleaned them up, but that didn't help. Whatever it was, it was > fixed in between 5.2Beta and 5.2RC1. I'm not having any performance > problems with system scope threads at all, and SMP works. Overall > performance is dramatically better than it had been previously. I'll try > process-scope kse threads again soon. I'm just happy I don't need to move > to a different platform. > > Now, I just have to track down why I'm getting EAGAIN from sendfile() > when I'm not using non-blocking sockets... Yes, well, try digging in the kernel for that. Neither libthr or libkse do anything WRT sendfile(), while libc_r needs a wrapper for it. -- Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10312130217220.29477-100000>