public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Subject: [patch 2.5.51] add wait_event() to <linux/completion.h>
Date: Wed, 11 Dec 2002 21:04:51 -0800	[thread overview]
Message-ID: <3DF818F3.6050308@pacbell.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Folk periodically talk about evolving the "struct completion"
support ... here's one:

   int wait_event (struct completion *x, signed long timeout_jiffies);

Returns zero if the event happened, nonzero if it timed out.
An example timeout action might be to cancel a request then
use wait_for_completion(x) to synchronize with that.

It's been behaving for me so far.  Questions from me:

- Is this appropriate to merge as-is?  The tradeoff I'm
   thinking of is code duplication; this patch avoids it
   ("smaller==better" rule-of-thumb) but maybe someone has
   real tuning knowledge, or a "standard" lk policy applies.
   Or there might be bugs or api transgressions.

- One routine was unavailable to modules; now exported.
   That seemed to just be an oversight.

This doesn't add an "interruptible wait" api mode, which
I'd expect some others might find a use for.  This patch
will let us clean up some dubious code in usbcore which
is more or less trying to do a wait_event().

Thanks in advance for any comments.

- Dave

[-- Attachment #2: sched.patch --]
[-- Type: text/plain, Size: 1730 bytes --]

--- ./include/linux-dist/completion.h	Sun Dec  8 10:57:47 2002
+++ ./include/linux/completion.h	Mon Dec  9 15:11:51 2002
@@ -28,6 +28,7 @@
 }
 
 extern void FASTCALL(wait_for_completion(struct completion *));
+extern int FASTCALL(wait_timeout(struct completion *, signed long jiffies));
 extern void FASTCALL(complete(struct completion *));
 extern void FASTCALL(complete_all(struct completion *));
 
--- ./kernel-dist/ksyms.c	Sun Dec  8 10:57:48 2002
+++ ./kernel/ksyms.c	Mon Dec  9 15:13:47 2002
@@ -404,7 +404,9 @@ EXPORT_SYMBOL(autoremove_wake_function);
 
 /* completion handling */
 EXPORT_SYMBOL(wait_for_completion);
+EXPORT_SYMBOL(wait_timeout);
 EXPORT_SYMBOL(complete);
+EXPORT_SYMBOL(complete_all);
 
 /* The notion of irq probe/assignment is foreign to S/390 */
 
--- ./kernel-dist/sched.c	Sun Dec  8 10:57:48 2002
+++ ./kernel/sched.c	Mon Dec  9 15:34:36 2002
@@ -1204,6 +1204,11 @@ void complete_all(struct completion *x)
 
 void wait_for_completion(struct completion *x)
 {
+	wait_timeout (x, MAX_SCHEDULE_TIMEOUT);
+}
+
+int wait_timeout(struct completion *x, signed long timeout_jiffies)
+{
 	might_sleep();
 	spin_lock_irq(&x->wait.lock);
 	if (!x->done) {
@@ -1214,13 +1219,19 @@ void wait_for_completion(struct completi
 		do {
 			__set_current_state(TASK_UNINTERRUPTIBLE);
 			spin_unlock_irq(&x->wait.lock);
-			schedule();
+			timeout_jiffies = schedule_timeout(timeout_jiffies);
+			if (timeout_jiffies == 0) {
+				__remove_wait_queue(&x->wait, &wait);
+				/* caller should wait again */
+				return 1;
+			}
 			spin_lock_irq(&x->wait.lock);
 		} while (!x->done);
 		__remove_wait_queue(&x->wait, &wait);
 	}
 	x->done--;
 	spin_unlock_irq(&x->wait.lock);
+	return 0;
 }
 
 #define	SLEEP_ON_VAR				\

             reply	other threads:[~2002-12-12  4:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  5:04 David Brownell [this message]
     [not found] <200212120746.gBC7kR482233@sullivan.realtime.net>
2002-12-12 18:53 ` [patch 2.5.51] add wait_event() to <linux/completion.h> David Brownell

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=3DF818F3.6050308@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.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