Date: Fri, 20 Jul 2001 08:48:32 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Peter Pentchev <roam@orbitel.bg> Cc: Louis-Philippe Gagnon <louisphilippe@macadamian.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: flock/pthread bug? Message-ID: <3B5852D0.AF5F3569@mindspring.com> References: <Pine.BSF.4.21.0107181320030.94740-100000@InterJet.elischer.org> <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> <3B5690A1.8EDD0812@mindspring.com> <203501c11059$35755420$2964a8c0@macadamian.com> <20010719194735.D10583@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Pentchev wrote: > I don't know if Terry was talking about the sched_yield() syscall, > but if he was, then sched_yield(2) exists, at least in 4.x, and is > documented as POSIX-compliant. No. He needs to yield the system CPU, not the CPU for his particular thread. In the user space threads library scheduler, you will just be yielding to another thread. -- Terry 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?3B5852D0.AF5F3569>