All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
	Brian Bunker <brian@purestorage.com>,
	dm-devel@lists.linux.dev, Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH v3 2/5] libmpathutil: add generic implementation for checker thread runners
Date: Tue, 28 Apr 2026 13:46:09 -0400	[thread overview]
Message-ID: <afDyYXIY2nyuI7Ij@redhat.com> (raw)
In-Reply-To: <20260428114942.292307-3-mwilck@suse.com>

On Tue, Apr 28, 2026 at 01:49:39PM +0200, Martin Wilck wrote:
> This code adds a generic, abstract implementation of the kind of threads we
> need for checkers: detached threads that may time out. The design is such
> that these threads never access any memory of the calling program,
> simplifying the management of lifetimes of objects.
> 
> See the documentation of the API in "runner.h".
> 
> Signed-off-by: Martin Wilck <mwilck@suse.com>

Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>


  reply	other threads:[~2026-04-28 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 11:49 [PATCH v3 0/5] multipath-tools: generic async threads for TUR checker Martin Wilck
2026-04-28 11:49 ` [PATCH v3 1/5] multipathd: get_new_state: map PATH_TIMEOUT to PATH_DOWN Martin Wilck
2026-04-28 11:49 ` [PATCH v3 2/5] libmpathutil: add generic implementation for checker thread runners Martin Wilck
2026-04-28 17:46   ` Benjamin Marzinski [this message]
2026-04-28 11:49 ` [PATCH v3 3/5] multipath-tools tests: add test program for " Martin Wilck
2026-04-28 17:46   ` Benjamin Marzinski
2026-04-28 11:49 ` [PATCH v3 4/5] libmultipath: TUR checker: use runner threads Martin Wilck
2026-04-28 11:49 ` [PATCH v3 5/5] libmultipath: tur checker: improve tur_deep_sleep() test Martin Wilck

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=afDyYXIY2nyuI7Ij@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=brian@purestorage.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=martin.wilck@suse.com \
    --cc=mwilck@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.