mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/8 v3] Make wake_up_{bit,var} less fragile
Date: Wed, 25 Sep 2024 15:24:03 +1000	[thread overview]
Message-ID: <20240925053118.3956520-1-neilb@suse.de> (raw)

Hi,

 this is a revised set of patches for cleaning up wake_up_bit and
 wake_up_var and related.  They are result of more proof reading, and of
 trying to make use of the new interfaces anywhere in the kernel where
 these interfaces are used.

 This should apply after -rc1, or at least after the block tree is merged.

 Note that on current master the cause a build error in bcachefs as it
 hasn't been updated with the new i_state bit management.

 Apart from proof-reading fixes this series adds to the previous series:

 - adds wait_var_event_any_lock() which can be used with any lock for
   which there are foo_lock and foo_unlock functions.  This is useful to
   deal with places that want to call filemap_invalidate_unlock/lock
   while waiting for a var

 - adds wait_var_event_io() for io_schedule waits - xfs can use this.

 - as a bonus, softirq gets some improvements to waiting.

Thanks,
NeilBrown


 [PATCH 1/8] block: change wait on bd_claiming to use a var_waitqueue,
 [PATCH 2/8] sched: change wake_up_bit() and related function to
 [PATCH 3/8] sched: Improve documentation for wake_up_bit/wait_on_bit
 [PATCH 4/8] sched: Document wait_var_event() family of functions and
 [PATCH 5/8] sched: Add test_and_clear_wake_up_bit() and
 [PATCH 6/8] sched: Add wait/wake interface for variable updated under
 [PATCH 7/8] sched: add wait_var_event_io()
 [PATCH 8/8] softirq: use bit waits instead of var waits.

             reply	other threads:[~2024-09-25  5:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  5:24 NeilBrown [this message]
2024-09-25  5:24 ` [PATCH 1/8] block: change wait on bd_claiming to use a var_waitqueue, not a bit_waitqueue NeilBrown
2024-09-25  5:24 ` [PATCH 2/8] sched: change wake_up_bit() and related function to expect unsigned long * NeilBrown
2024-09-25  5:24 ` [PATCH 3/8] sched: Improve documentation for wake_up_bit/wait_on_bit family of functions NeilBrown
2024-09-25  5:24 ` [PATCH 4/8] sched: Document wait_var_event() family of functions and wake_up_var() NeilBrown
2024-09-25  5:24 ` [PATCH 5/8] sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() NeilBrown
2024-09-25  5:24 ` [PATCH 6/8] sched: Add wait/wake interface for variable updated under a lock NeilBrown
2024-09-25  5:24 ` [PATCH 7/8] sched: add wait_var_event_io() NeilBrown
2024-09-25  5:24 ` [PATCH 8/8] softirq: use bit waits instead of var waits NeilBrown

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=20240925053118.3956520-1-neilb@suse.de \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®