:OK, so let's say I did spend some time implementing it in terms of semget()
:and semop(). Would you be totally apalled if the performance turned out to
:be about the same as using a single socketpair? Do you have a very strong
:feeling that it should be significantly better. [Again, under
:3.4-release.] I don't think I've done anything egregious, but things don't
:seem much better. Unfortunately, I'll have to wait until tomorrow morning
:to rip things out and make a suitable example program for posting.
:
:Actually, the performance profile does seem different (for lower loads, the
:semaphore solution seems more efficient), but the performance limits seem
:much the same between the single socketpair and semaphore versions when I
:starts using 16-20 worker processes. It's possible that I'm doing
:..
:
:Thanks,
:scott
Well, when all else fails --- go back to individual pipes.
What else could be tried... you could try surrounding the read()
with an flock() pair. I don't know if flock() uses the more optimal
wakeup code or not.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
