agent: Avoid tight timer tick when possible.
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Tue, 1 Nov 2016 04:14:10 +0000 (00:14 -0400)
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Sun, 30 Sep 2018 16:40:42 +0000 (17:40 +0100)
commit005acba87159a8d1bfbd1d31513a7952d433dd66
tree805534f0dd0231a59976f9be880c0bf8123f8938
parent1b688b7d8d83dc92245898ac70feee97b71c926e
agent: Avoid tight timer tick when possible.

* agent/gpg-agent.c (need_tick): Evaluate whether the short-phase
handle_tick() is needed.
(handle_connections): On each cycle of the select loop, adjust whether
we should call handle_tick() or not.
(start_connection_thread_ssh, do_start_connection_thread): Signal the
main loop when the child terminates.
* agent/call-scd.c (start_scd): Call interrupt_main_thread_loop() once
the scdaemon thread context has started up.

--

With this change, an idle gpg-agent that has no scdaemon running only
wakes up once a minute (to check_own_socket).

Thanks to Ian Jackson and NIIBE Yutaka who helped me improve some of
the blocking and corner cases.

Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Gbp-Pq: Topic gpg-agent-idling
Gbp-Pq: Name agent-Avoid-tight-timer-tick-when-possible.patch
agent/call-scd.c
agent/gpg-agent.c