user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/7] cindex: fix FreeBSD freezes
Date: Wed,  5 Apr 2023 11:26:51 +0000	[thread overview]
Message-ID: <20230405112658.90216-1-e@80x24.org> (raw)

PATCH 6/7 is the fix.  It took me a while to realize how to fix it.

1-5 improve parallelism and reduce resource usage while limiting
the workaround to a single callsite in #6.  And #7 is just a
cleanliness fix.

Eric Wong (7):
  ipc: support awaitpid in WQ workers
  cindex: do prune work while waiting for `git log -p'
  cindex: share PktOp socket across prune workers
  cindex: share PktOp across indexing workers
  cindex: enter event loop once per run
  cindex: workaround for FreeBSD missing SIGCHLD
  cindex: reset DS internals on cidx_run completion

 MANIFEST                         |   1 +
 lib/PublicInbox/CidxLogP.pm      |  29 ++++
 lib/PublicInbox/CodeSearchIdx.pm | 290 ++++++++++++++++---------------
 lib/PublicInbox/IPC.pm           |  11 +-
 4 files changed, 184 insertions(+), 147 deletions(-)
 create mode 100644 lib/PublicInbox/CidxLogP.pm

             reply	other threads:[~2023-04-05 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 11:26 Eric Wong [this message]
2023-04-05 11:26 ` [PATCH 1/7] ipc: support awaitpid in WQ workers Eric Wong
2023-04-05 11:26 ` [PATCH 2/7] cindex: do prune work while waiting for `git log -p' Eric Wong
2023-04-05 11:26 ` [PATCH 3/7] cindex: share PktOp socket across prune workers Eric Wong
2023-04-05 11:26 ` [PATCH 4/7] cindex: share PktOp across indexing workers Eric Wong
2023-04-05 11:26 ` [PATCH 5/7] cindex: enter event loop once per run Eric Wong
2023-04-05 11:26 ` [PATCH 6/7] cindex: workaround for FreeBSD missing SIGCHLD Eric Wong
2023-04-05 11:26 ` [PATCH 7/7] cindex: reset DS internals on cidx_run completion Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230405112658.90216-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).