Date: Fri, 29 Jun 2001 18:33:52 +0300 From: Peter Pentchev <roam@orbitel.bg> To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net> Cc: Terry Lambert <tlambert2@mindspring.com>, Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r locking... why? Message-ID: <20010629183352.D535@ringworld.oblivion.bg> In-Reply-To: <Pine.LNX.4.20.0106291334350.7587-100000@www.everquick.net>; from eddy%2Bpublic%2Bspam@noc.everquick.net on Fri, Jun 29, 2001 at 03:19:47PM %2B0000 References: <3B3C3346.E5496485@mindspring.com> <Pine.LNX.4.20.0106291334350.7587-100000@www.everquick.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 29, 2001 at 03:19:47PM +0000, E.B. Dreger wrote: > > The threads scheduler is in user space. It converts a > > blobking call into a non-blocking call plus a context > > switch. THus blocking _IS_ a problem. > > Bad wording on my part again; perhaps "a problem that I [think > that] I have handled" is better. I'm use nb calls if possible; > else I have a long-running worker thread. I hope you understand that when the worker thread blocks, it's the process that blocks, and none of the other threads can run until the end of the syscall. > After my recent question regarding AIO, it looks like it's time > to bite the bullet and use that as well. G'luck, Peter -- If this sentence were in Chinese, it would say something else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010629183352.D535>