Michael, What does the thundering herd problem have to do with select vs poll? The only typically useful advantages of poll over select that I am aware of are that poll can monitor more descriptors than select and that it can monitor a large number of descriptors more efficiently -- but this efficiency issue has nothing to do with thundering herd.
I'm having trouble with the context here. Rich is talking about simply using select/poll to monitor multiple sockets. Thundering herd is a problem when a large number of threads are monitoring the same events. While select/poll can be used in such a way that thundering herd can be a problem, for the simple single-thread select/poll loop it just isn't in the picture -- how can a single thread suffer from the thundering herd problem? Regards, Steven -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Sierchio Sent: Tuesday, 18 October 2005 2:49 AM To: openssl-dev@openssl.org Subject: Re: ideas on replacing where ERR_STATE is stored? Steven Reddie wrote: > Hi Michael, > > I'm familiar with that approach, having used it many times myself. > The choice of poll over select isn't important since they're basically > the same; in fact, poll is sometimes implemented with select. Who implements poll with select should suffer a fate worse than death -- waking up a thousand sleeping threads to see if one has some i/o ready is what poll was designed to avoid. "But that's just my opinion..." ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
