[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libmicrohttpd] Thread modes and event looks & MHD_USE_THREAD_PER_CO

From: Christian Grothoff
Subject: Re: [libmicrohttpd] Thread modes and event looks & MHD_USE_THREAD_PER_CONNECTION
Date: Sun, 30 Aug 2015 14:58:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0

Dear Allan,

I checked the documentation and found that it was in one place simply
wrong and in others possibly confusing.  Specifically,

> ... and only works in conjunction with MHD_USE_THREAD_PER_CONNECTION

was totally wrong as this is the only case where
MHD_USE_EPOLL_LINUX_ONLY does not work (because it makes no sense: there
is only one socket if we run a thread per connection, so using
poll() instead of epoll() is always better/simpler/gives same O(1)

I've clarified the documentation in SVN 36283.

Thanks for pointing this out!

Happy hacking!


On 08/27/2015 10:56 AM, Allan Wind wrote:
> Hi,
> I was reviewing at the documentation, and I noticed in the 
> "Thread modes and event loops" section (epoll, external) = 
> (epoll, internal) = (epoll, thread pool) = yes.  Later, in the 
> Constants section however, for MHD_USE_EPOLL_LINUX_ONLY, it says:
> ... and only works in conjunction with MHD_USE_THREAD_PER_CONNECTION
> Both cannot be correct, or am I missing something here?
> I understand from the archives, that external the thread mode, 
> means you have to use select in your own event loop.  Is this 
> still the case?
> /Allan

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]