I would suggest looking at the entry points to the kernel in a top-down approach, start with system calls and interrupts. These two things are what tell the kernel what to do, they would be the best place to start to see what is really going on underneath. I found that this approach makes it easier to understand the lower level stuff much easier since you know it purpose in the upper level stuff. On Monday 04 August 2003 12:52 pm, Loic Domaigne wrote: > Hello guys! > > I'd like to get a deeper understanding about the Linux kernel. > First I'd like to concentrate on the core (VM/Scheduler/Process etc.). > > I have a decent knowledge of Linux/Unix System Programming, > and master C. I have bought several books on Linux/Unix internals, > including: > > "Understanding the Linux Kernel", 2ed, Daniel P. Bovet, Marco Cesati. > > > I found already on the net several nice docs about Linux kernels. > However, the problem is that the information are spread accross the > docs, and it's hard to figure out the "big picture"... > > Well, I'm a practice oriented guys. To really understand how the > kernel works, I have to experiment and trace step by step what the > kernel does. I plan to use UML, since it works in user space (and > as result, it makes life easier to gdb the kernel). > > Do you have any other suggestions/advices ?? > > > Regards, > Loic. -- Tom Bradley Software Engineer Jaycor / Titan Systems -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
