Event loops: served on by default, the data relayed by the loops

loopmode is cb unless a configuration says otherwise, as -L2 had it
for a service: its clients on event loops, a connection's data relayed
by the loop itself where nothing but the sockets is between its sides.
A service whose clients cannot share a thread (threadperclient: PAM,
LDAP, FilePlugin, names resolved by the system, -ne) or listening for
connections back (-R) still gives each a thread, as do the standalone
services and builds without fibers. loopmode on and -L keep the loops
with the relay on the client's stack; loopmode off and -L0 a thread
for each client.

The man page tells of cb. tests/run.py --loopmode takes the mode
(cb, on, off) to give every configuration, with two loops; the Linux
workflow runs the suite once more with a thread for each client, which
is no longer what a configuration gets by default.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Vladimir DubrovinandClaude Opus 5.5 committed 2026-10-28 11:49:51 +03:00
1 parent 143158e97f
commit 023eb8f830
8 files changed
+33 -18

No files matched your search

+2 -1
View File
@@ -1009,7 +1009,8 @@ struct extparam {
int filtermaxsize;
int poolmax, pooltimeout; /* threadpool: idle workers kept, -1 automatic */
int loops; /* threads serving clients on event loops, 0: a CPU each */
int loopmode; /* services from here on serve clients on loops */
int loopmode; /* services from here on serve clients on loops: 1, and
relay their data there: 2 */
int gracetraf, gracenum, gracedelay;
int maxseg;
unsigned char **archiver;