The
HyperNews
Linux KHG
Discussion Pages
|
Next-in-Thread
|
Next Response
|
Previous Response
|
Next Thread
|
Misc questions on the kernel
-
Base:
The Linux Kernel Hackers' Guide
Keywords: device driver task virtual memory
Date: Fri, 07 Jun 1996 14:47:45 GMT
From:
hasdi@engin.umich.edu (Hasdi)
Body-URL: http://www-personal.engin.umich.edu/~hasdi/linux.html
Hi guys!!!
I am relatively new to linux-kernel hacking so please be nice. :)
I have some questions that are running crazy in my mind but too
afraid to ask in comp.os.linux.development.apps:
- Why is it difficult to make kernel memory swappable?
- Why can't the kernel be peremptive? Why can't the kernel have certain
points where it is safe to switch?
- Why does task switch take so long? How many things do you have to
resolve before passing control to another task? Is scheduler called at
every timer interrupt? task switch==context switch?
- Why is /dev filesystem not implemented the same way as /proc pseudo
filesystem? Why must inodes be used in /dev filesystem?
- What's the deal with major and minor number? Isn't it a major pain to
keep track of numbers? Why can't /dev be organized like /dev/scsi/.
/dev/hd/. /dev/serial/. /dev/graphics/. /dev/. etc etc; why are all the
device drivers lumped into a single directory?
- Is there a reason why all device drivers must be lumped together in
the kernel or as kernel modules? Is it possible to have setuid root driver
program that registers/attaches itself to the kernel and detaches itself
when you kill it? You know, like in DOS?
- Is possible to directly call a routine in another process and skip
all sockets/SysV IPC nonsense? Even if it has to pass through a kernel
layer first?
Thanks in Advance!
Hasdi
Responses
[Embed Depth:
1
2
3
All]
[Outline Depth:
1
2
3
9
All]
- 1.
Untitled (benschop@eb.ele.tue.nl)
- 2.
Untitled (benschop@eb.ele.tue.nl)