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] inboxidle: avoid needless syscalls on refresh
Date: Sat, 26 Dec 2020 09:36:31 +0000	[thread overview]
Message-ID: <20201226093631.14313-1-e@80x24.org> (raw)

We don't have to replace a bunch of existing watches
with identical new ones.  On Linux with Linux::Inotify2
installed, this avoids a storm of inotify_add_watch(2)
and inotify_rm_watch(2) syscalls on SIGHUP with -imapd
and "-extindex --watch"
---
 lib/PublicInbox/InboxIdle.pm | 15 ++++++++++++---
 t/imapd.t                    | 26 +++++---------------------
 2 files changed, 17 insertions(+), 24 deletions(-)

diff --git a/lib/PublicInbox/InboxIdle.pm b/lib/PublicInbox/InboxIdle.pm
index 69da5f4f..35aed696 100644
--- a/lib/PublicInbox/InboxIdle.pm
+++ b/lib/PublicInbox/InboxIdle.pm
@@ -24,17 +24,26 @@ sub in2_arm ($$) { # PublicInbox::Config::each_inbox callback
 	my $dir = $ibx->{inboxdir};
 	my $inot = $self->{inot};
 	my $cur = $self->{pathmap}->{$dir} //= [];
+	my $lock = "$dir/".($ibx->version >= 2 ? 'inbox.lock' : 'ssoma.lock');
 
 	# transfer old subscriptions to the current inbox, cancel the old watch
-	if (my $old_ibx = $cur->[0]) {
+	my $old_ibx = $cur->[0];
+	$cur->[0] = $ibx;
+	if ($old_ibx) {
 		$ibx->{unlock_subs} and
 			die "BUG: $dir->{unlock_subs} should not exist";
 		$ibx->{unlock_subs} = $old_ibx->{unlock_subs};
+
+		# Linux::Inotify2::Watch::name matches if watches are the
+		# same, no point in replacing a watch of the same name
+		if ($cur->[1]->name eq $lock) {
+			$self->{on_unlock}->{$lock} = $ibx;
+			return;
+		}
+		# rare, name changed (v1 inbox converted to v2)
 		$cur->[1]->cancel; # Linux::Inotify2::Watch::cancel
 	}
-	$cur->[0] = $ibx;
 
-	my $lock = "$dir/".($ibx->version >= 2 ? 'inbox.lock' : 'ssoma.lock');
 	if (my $w = $cur->[1] = $inot->watch($lock, $IN_MODIFY)) {
 		$self->{on_unlock}->{$w->name} = $ibx;
 	} else {
diff --git a/t/imapd.t b/t/imapd.t
index 43ec200c..63a86e71 100644
--- a/t/imapd.t
+++ b/t/imapd.t
@@ -296,27 +296,11 @@ $pi_cfg->each_inbox(sub {
 
 	# ensure IDLE persists across HUP, w/o extra watches or FDs
 	$td->kill('HUP') or BAIL_OUT "failed to kill -imapd: $!";
-	SKIP: {
-		skip 'no inotify fdinfo (or support)', 2 if !@ino_info;
-		my (@tmp, %prev);
-		local $/ = "\n";
-		my $end = time + 5;
-		until (time > $end) {
-			select undef, undef, undef, 0.01;
-			open my $fh, '<', $ino_fdinfo or
-						BAIL_OUT "$ino_fdinfo: $!";
-			%prev = map { $_ => 1 } @ino_info;
-			@tmp = grep(/^inotify wd:/, <$fh>);
-			if (scalar(@tmp) == scalar(@ino_info)) {
-				delete @prev{@tmp};
-				last if scalar(keys(%prev)) == @ino_info;
-			}
-		}
-		is(scalar @tmp, scalar @ino_info,
-			'old inotify watches replaced');
-		is(scalar keys %prev, scalar @ino_info,
-			'no previous watches overlap');
-	};
+	for my $n (1..2) { # kick the event loop so we know HUP is done
+		my $m = $imap_client->new(%mic_opt);
+		ok($m->login && $m->IsAuthenticated && $m->logout,
+			"connection $n works after HUP");
+	}
 
 	open($fh, '<', 't/data/0001.patch') or BAIL_OUT("open: $!");
 	run_script(['-mda', '--no-precheck'], $env, { 0 => $fh }) or

             reply	other threads:[~2020-12-26  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26  9:36 Eric Wong [this message]
2020-12-26 20:11 ` [PATCH] inboxidle: avoid needless syscalls on refresh 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: http://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=20201226093631.14313-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).