Date: Thu, 15 Jun 2006 17:33:09 +0800 From: David Xu <davidxu@freebsd.org> To: Xin LI <delphij@delphij.net> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys sched.h src/sys/posix4 ksched.c src/sys/kern sched_4bsd.c sched_core.c sched_ule.c Message-ID: <44912955.3000307@freebsd.org> In-Reply-To: <1150363262.937.44.camel@spirit> References: <200606150637.k5F6bdax000157@repoman.freebsd.org> <1150363262.937.44.camel@spirit>
next in thread | previous in thread | raw e-mail | index | archive | help
Xin LI wrote: > Hi, David, > > 在 2006-06-15四的 06:37 +0000，David Xu写道： > >>davidxu 2006-06-15 06:37:39 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/sys sched.h >> sys/posix4 ksched.c >> sys/kern sched_4bsd.c sched_core.c sched_ule.c >> Log: >> Add scheduler API sched_relinquish(), the API is used to implement >> yield() and sched_yield() syscalls. Every scheduler has its own way >> to relinquish cpu, the ULE and CORE schedulers have two internal run- >> queues, a timesharing thread which calls yield() syscall should be >> moved to inactive queue. > > > A question that might be related: We have sched_sizeof_proc(), etc. in > every scheduler, which returns a constant. Is it worthy to convert them > to constants that just expand inline during the kernel compile? > > Cheers, If you think this is right, we don't need td_kse either, we could include a scheduler header file by proc.h, and all scheduler data can be embedded into thread structure, this will eliminate many indirect pointer references in scheduler code, but some people are already working on kernel code cleanup, I won't touch this, this may happen in future though. Regards,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44912955.3000307>