Re: My overview of the kernel --> do I have it correct ??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi William,

On Thu, Jul 10, 2008 at 10:49:23AM -0400, William Case wrote:

>         The tables often have pointers to each other in order to build
>         up a full process.  Some of the most important tables are; the
>         inode, the file descriptor, the socket, the process, the
>         interrupt handler, the signal handler and the error handler
>         tables. (If I am on the right track, but have forgotten an
>         important table please tell me).

What I would add here are device drivers. They are also collected in a
table, with function pointers to offer their functionality. Still, when
dealing with hardware at this level, I think a reduction to a "table
entry" is not enough. There is quite some logic involved, which is
mostly pure code to handle states of the hardware. It is the end of all
abstractions :)

In general, your description sounds a bit as if code is
underrepresented, but probably you don't mean it that way. The general
approach should hold, IMHO.

All the best,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux