Date: Mon, 13 Nov 2006 21:27:58 +0800 (CST) From: shin_ta <g9471029@pu.edu.tw> To: freebsd-questions@freebsd.org Subject: help Message-ID: <15138958.7381163424479193.JavaMail.root@judea>
next in thread | raw e-mail | index | archive | help
I have some questions about the design and implementation of the FreeBSD op= erating system 1. FreeBSD used System call, Hardware interrupt, Hardware trap, an= d Software-initiated trap to entry into the system kernel. What is the deta= iled operation and why FreeBSD design by this way? =20 2. In FreeBSD 5.2, interrupt has its own context stack, what are t= he influences to each aspect of the operating system?(like bottom half of k= ernel, top half of kernel =E2=80=A6) =20 3. What is the basic function of the signal? Which main data struc= tures are about signal? Which procedures are related in signal? =20 4. Why signal handler routine design in user-level but not in kern= el-level? =20 5. After the system call completes, the system-call exit code firs= t checks for a posted signal, after checking for posted signals, the system= -call exit code checks to see whether any process has a priority higher tha= n that of the currently running one. Why FreeBSD do this check at this time= ? =20 6. The ULE scheduler was developed as part of the overhaul of Free= BSD to support SMP. Why the ULE scheduler relatively suitable for the SMP s= ystem than 4.4BSD timeshareing scheduler. =20 7. FreeBSD uses pager to manage the memory. Different memory objec= ts have different pager to deal with. Why FreeBSD designed by this way?=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15138958.7381163424479193.JavaMail.root>