<br><br><div><span class="gmail_quote">On 12/12/06, <b class="gmail_sendername">Kevin Sanders</b> <<a href="mailto:newroswell@gmail.com">newroswell@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 12/11/06, Zhu Han <<a href="mailto:schumi.han@gmail.com">schumi.han@gmail.com</a>> wrote:<br><br>Ah, that's a good point. We're pretty sure it was 0, which means<br>allow as many as physical processors, but if it was 1, that would
<br>explain it. Another clue with this is that if the first thread<br>blocked (in our test we called Sleep(60000), one of the other IOCP<br>threads would then be able to pop that sockets completion<br>notification.</blockquote>
<div><br>If the number is 0, the platform is UP and the IOCP thread never blocks at any point, it is possible another thread will never get the chance be waken up.<br><br>Can you reproduce the CPU affinity problem?<br></div>
<br></div>-- <br>best regards,<br>hanzhu