[systemd-devel] [PATCH] core/socket: we only want one event on standard sockets
David Timothy Strauss
david at davidstrauss.net
Mon Nov 25 20:44:00 PST 2013
On Tue, Nov 26, 2013 at 2:35 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> Not following here. What precisely does this fix, can you elaborate?
>
> We currently turn off the poll for the socket fds as soon as we queued
> the service socket, so that we don't get woken up anymore. What would
> EPOLLET do good here?
I think he's been working on having the "distribute" pool scale up
on-demand, which would involve systemd getting events on new
connections coming into the listener socket. More specifically, I
think he intends to, as each new connection comes in, check if we've
maxed out the number of processes. If not, spin another one up.
Presumably, we'd drop the listener once the max-size pool is running.
More information about the systemd-devel
mailing list