os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add scheduler cleanup and resolution issue to must fix items.

Browse source
This commit is contained in:
Robert Watson 2004-07-15 13:23:18 +00:00
parent f035a2b9bd
commit b50ded7402
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=21517
1 changed files with 17 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
en/releases/5.3R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.27 2004/07/15 12:45:37 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.28 2004/07/15 13:06:24 rwatson Exp $">
<!ENTITY title "FreeBSD 5.3 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -132,6 +132,22 @@
models.</td>
</tr>
<tr>
<td>Scheduler cleanup and resolution</td>
<td>&status.wip;</td>
<td>--</td>
<td>Currently, two schedulers are present: SCHED_ULE (default), an
SMP-optimized scheduler created as part of SMPng, and SCHED_4BSD,
an SMP-adapted version of the original 4BSD scheduler. They have
quite different performance properties, with ULE providing strong
interactivity characteristics, and performing quite well in a
number of benchmarks, and 4BSD showing greater strength in IPC
intensive user space benchmarks, such as databases. One of these
schedulers must be the default for 5.3, and whichever one it is,
it requires careful measurement, analysis, and optimization before
the release in order to address its defficiences.</td>
</tr>
</table>
<h3>Desired features for 5.3-RELEASE</h3>