Linux CXL
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Fabio M. De Francesco"
	<fabio.maria.de.francesco@linux.intel.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	Dan Williams <dan.j.williams@intel.com>,
	<linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, <linux-cxl@vger.kernel.org>,
	"Fabio M. De Francesco"
	<fabio.maria.de.francesco@linux.intel.com>,
	Ira Weiny <ira.weiny@intel.com>
Subject: RE: [PATCH 1/2] cleanup: Add cond_guard() to conditional guards
Date: Mon, 5 Feb 2024 11:13:57 -0800	[thread overview]
Message-ID: <65c133751a7_4e7f52946@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20240204173105.935612-2-fabio.maria.de.francesco@linux.intel.com>

Fabio M. De Francesco wrote:
> Add cond_guard() macro to conditional guards.
> 
> cond_guard() is a guard to be used with the conditional variants of locks,
> like down_read_trylock() or mutex_lock_interruptible().
> 
> It takes a statement (or more statements in a block) that is passed to its

s/or more statements in a block/or statement-expression)/

s/to its/as its/

> second argument. That statement (or block) is executed if waiting for a
> lock is interrupted or if a _trylock() fails in case of contention.
> 
> Usage example:
> 
> 	cond_guard(rwsem_read_try, { printk(...); return 0; }, &semaphore);

Missed commenting on this in the last posting, but multi-statement fail
cases that print and return 0 are unlikely to ever be the common case. I
think the most simple to understand example is an interruptible lock
that returns -EINTR on failure:

	cond_guard(mutex_intr, return -EINTR, &mutex);

...and then maybe mention that _fail can be a statement-expression if
needed.

> Consistenly with the other guards, locks are unlocked at the exit of the

s/Consistenly with the other guards/Consistent with other usage of guard()/

  parent reply	other threads:[~2024-02-05 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 17:31 [PATCH 0/2] Add cond_guard() to conditional guards Fabio M. De Francesco
2024-02-04 17:31 ` [PATCH 1/2] cleanup: " Fabio M. De Francesco
2024-02-05 11:09   ` Jonathan Cameron
2024-02-05 17:04   ` Ira Weiny
2024-02-05 19:13   ` Dan Williams [this message]
2024-02-04 17:31 ` [PATCH 2/2] cxl/region: Use cond_guard() in show_targetN() Fabio M. De Francesco
2024-02-05 11:11   ` Jonathan Cameron
2024-02-05 17:06   ` Ira Weiny
2024-02-05 10:56 ` [PATCH 0/2] Add cond_guard() to conditional guards Jonathan Cameron

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=65c133751a7_4e7f52946@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=fabio.maria.de.francesco@linux.intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox