Files
kernel/include/linux
Peter Zijlstra 6b2bb7265f sched/wait: Introduce wait_var_event()
As a replacement for the wait_on_atomic_t() API provide the
wait_var_event() API.

The wait_var_event() API is based on the very same hashed-waitqueue
idea, but doesn't care about the type (atomic_t) or the specific
condition (atomic_read() == 0). IOW. it's much more widely
applicable/flexible.

It shares all the benefits/disadvantages of a hashed-waitqueue
approach with the existing wait_on_atomic_t/wait_on_bit() APIs.

The API is modeled after the existing wait_event() API, but instead of
taking a wait_queue_head, it takes an address. This addresses is
hashed to obtain a wait_queue_head from the bit_wait_table.

Similar to the wait_event() API, it takes a condition expression as
second argument and will wait until this expression becomes true.

The following are (mostly) identical replacements:

	wait_on_atomic_t(&my_atomic, atomic_t_wait, TASK_UNINTERRUPTIBLE);
	wake_up_atomic_t(&my_atomic);

	wait_var_event(&my_atomic, !atomic_read(&my_atomic));
	wake_up_var(&my_atomic);

The only difference is that wake_up_var() is an unconditional wakeup
and doesn't check the previously hard-coded (atomic_read() == 0)
condition here. This is of little concequence, since most callers are
already conditional on atomic_dec_and_test() and the ones that are
not, are trivial to make so.

Tested-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2018-03-20 08:23:17 +01:00
..
2017-11-28 16:30:38 +01:00
2018-01-01 22:54:42 -08:00
2018-02-20 11:34:54 +00:00
2018-01-02 13:59:16 -05:00
2017-11-30 16:55:35 +00:00
2018-02-06 18:32:44 -08:00
2017-12-19 16:35:34 -08:00
2018-01-03 14:03:48 +01:00
2017-11-27 16:19:56 -05:00
2018-02-12 15:59:08 +00:00
2018-01-01 12:40:27 -07:00
2018-01-25 14:10:39 -08:00
2018-02-26 12:32:42 -08:00
2018-02-26 09:48:42 -07:00
2018-01-16 00:04:19 +01:00
2018-02-06 16:41:29 -05:00
2018-01-17 11:30:16 +00:00
2017-12-29 21:13:04 +01:00
2018-02-24 01:43:47 +01:00
2017-12-01 13:09:40 -08:00
2018-01-03 11:00:22 -05:00
2018-01-31 17:18:38 -08:00
2018-01-28 22:17:24 -05:00
2018-01-08 08:22:45 -06:00
2018-01-17 15:25:50 +01:00
2018-01-25 08:48:20 -06:00
2018-01-08 08:22:45 -06:00
2017-12-14 16:00:49 -08:00
2018-01-31 17:18:40 -08:00
2018-01-31 17:18:37 -08:00
2018-02-01 11:40:07 -06:00
2018-01-19 16:50:53 -08:00
2017-12-16 02:05:48 +01:00
2018-02-06 16:41:28 -05:00
2017-12-11 14:37:11 -07:00
2017-11-29 22:16:31 +01:00
2018-01-29 12:02:54 -05:00
2018-01-18 11:56:49 +01:00
2018-01-15 12:07:46 -08:00
2018-01-15 09:35:45 +01:00
2018-02-06 18:32:47 -08:00
2018-01-09 16:27:43 +01:00
2018-02-06 18:32:44 -08:00
2017-12-20 09:53:54 -07:00
2017-11-27 16:19:54 -05:00