NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: misc/38979 (Document syscalls of src/sys/kern/sys_sched.c)

To: misc-bug-people%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,rmind%NetBSD.org@localhost,mm_lists%pulsar-zone.net@localhost
Subject: Re: misc/38979 (Document syscalls of src/sys/kern/sys_sched.c)
From: rmind%NetBSD.org@localhost
Date: Wed, 18 Jun 2008 08:22:32 +0000 (UTC)

Synopsis: Document syscalls of src/sys/kern/sys_sched.c

State-Changed-From-To: open->closed
State-Changed-By: rmind%NetBSD.org@localhost
State-Changed-When: Wed, 18 Jun 2008 08:22:31 +0000
State-Changed-Why:
Have you taken a look at sched(3) and affinity(3) man pages?
Scheduling functions are mostly documented.

Follow-Ups:
- Re: misc/38979 (Document syscalls of src/sys/kern/sys_sched.c)
  - From: Matthew Mondor

Prev by Date: kern/38980: sysmonread_power() has unreachable mutex_exit(), - or - locking it too complicated
Next by Date: kern/38981: FFS+softdep panic on !cv_has_waiters(&bp->b_done) (vfs_subr2.c:551)
Previous by Thread: kern/38980: sysmonread_power() has unreachable mutex_exit(), - or - locking it too complicated
Next by Thread: Re: misc/38979 (Document syscalls of src/sys/kern/sys_sched.c)
Indexes:

Home | Main Index | Thread Index | Old Index