From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: [PATCH] PR26775 interruptible/observable grooming
Date: Fri, 30 Oct 2020 13:36:49 +0100 [thread overview]
Message-ID: <e4e03616ed4833079850016a022b91f24af3f7b8.camel@klomp.org> (raw)
In-Reply-To: <20201029183036.GA11642@redhat.com>
Hi Frank,
On Thu, 2020-10-29 at 14:30 -0400, Frank Ch. Eigler via Elfutils-devel
wrote:
> Author: Frank Ch. Eigler <fche@redhat.com>
> Date: Thu Oct 29 14:25:18 2020 -0400
>
> PR26775: make grooming progress visible & interruptible
>
> On very large servers, it's desirable to be able to interrupt a rescan
> or groom cycle. SIGUSR[12] now do that. (Unfortunately, this is not
> practically testable in the testsuite, since these cycles are so fast
> on that small dataset.) We also expose more internal progress count
> about the grooming pass, so the administrator can assess possible need
> to interrupt.
Looks good to me. Agreed about not really being able to test this due
to timing.
Cheers,
Mark
next prev parent reply other threads:[~2020-10-30 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 18:30 Frank Ch. Eigler
2020-10-30 12:36 ` Mark Wielaard [this message]
2020-10-30 22:36 ` Frank Ch. Eigler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4e03616ed4833079850016a022b91f24af3f7b8.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
/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.
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).