k&r style removal in kern_synch.c
Peter Kadau
peter.kadau at tuebingen.mpg.de
Mon Jan 26 04:58:37 PST 2004
Hi !
The last commits woke up a personal thread ;-)
Remove K&R function style in kern_synch.c.
Remove comment on priority argument in tsleep().
(Or should the functionality be added again ?
I was a bit unsure about the YYY...)
Cheers
Peter
--
<peter.kadau at xxxxxxxxxxxxxxxx>
Campus der Max-Planck-Institute Tübingen
Netzwerk- und Systemadministration
Tel: +49 7071 601 598
Fax: +49 7071 601 616
Index: kern/kern_synch.c
===================================================================
RCS file: /local/dragonfly/src/sys/kern/kern_synch.c,v
retrieving revision 1.26
diff -u -r1.26 kern_synch.c
--- kern/kern_synch.c 7 Jan 2004 11:04:18 -0000 1.26
+++ kern/kern_synch.c 26 Jan 2004 12:52:18 -0000
@@ -350,26 +350,21 @@
/*
* General sleep call. Suspends the current process until a wakeup is
* performed on the specified identifier. The process will then be made
- * runnable with the specified priority. Sleeps at most timo/hz seconds
- * (0 means no timeout). If flags includes PCATCH flag, signals are checked
- * before and after sleeping, else signals are not checked. Returns 0 if
- * awakened, EWOULDBLOCK if the timeout expires. If PCATCH is set and a
- * signal needs to be delivered, ERESTART is returned if the current system
- * call should be restarted if possible, and EINTR is returned if the system
- * call should be interrupted by the signal (return EINTR).
+ * runnable. Sleeps at most timo/hz seconds (0 means no timeout).
+ * If flags includes PCATCH flag, signals are checked before and after
+ * sleeping, else signals are not checked. Returns 0 if awakened, EWOULDBLOCK
+ * if the timeout expires. If PCATCH is set and a signal needs to be delivered,
+ * ERESTART is returned if the current system call should be restarted
+ * if possible, and EINTR is returned if the system call should be
+ * interrupted by the signal (return EINTR).
*
* If the process has P_CURPROC set mi_switch() will not re-queue it to
* the userland scheduler queues because we are in a SSLEEP state. If
* we are not the current process then we have to remove ourselves from
* the scheduler queues.
- *
- * YYY priority now unused
*/
int
-tsleep(ident, flags, wmesg, timo)
- void *ident;
- int flags, timo;
- const char *wmesg;
+tsleep(void *ident, int flags, const char *wmesg, int timo)
{
struct thread *td = curthread;
struct proc *p = td->td_proc; /* may be NULL */
@@ -845,8 +840,7 @@
/* ARGSUSED */
static void
-sched_setup(dummy)
- void *dummy;
+sched_setup(void *dummy)
{
callout_init(&loadav_callout);
More information about the Submit
mailing list