Linux Data Structures
(*)block_dev_struct -> block_dev_struct data structures are used to register block devices as available for use by the buffer cache. They are held together in the blk_dev vector.
(*)buffer_head -> The buffer_head data structure holds information about a block buffer in the buffer cache.
(*)device -> Every network device in the system is represented by a device data structure.
(*)device_struct -> device_struct data structures are used to register character and block devices. (They hold the name and the set of file operations that can be used for this device). Each valid member of the chrdevs and blkdevs vectors represents a character or block device respectively.
(*)file -> Each open file, socket etcetera is represented by a file data structure.
(*)files_struct -> The files_struct data structure describes the files that a process has open.
(*)gendisk -> The gendisk data structure holds information about a hard disk. They are used during initialization when the disks are found and then probed for partitions.
(*)inode -> The VFS inode data structure holds information about a file or directory on disk.
(*)ipc_perm -> The ipc_perm data structure describes the access permissions of a System V IPC object.
(*)irqaction -> The irqaction data structure is used to describe the system's interrupt handlers.
(*)linux_binfmt -> Each binary file format that Linux understands is represented by a linux_binfmt data structure.
(*)mem_map_t -> The mem_map_t data structure (also known as page) is used to hold information about each page of physical memory.
(*)mm_struct -> The mm_struct data structure is used to describe the virtual memory of a task or process.
(*)pci_bus -> Every PCI bus in the system is represented by a pci_bus data structure.
(*)pci_dev -> Every PCI device in the system, including PCI-PCI and PCI-ISA bridge devices is represented by a pci_dev data structure.
(*)request -> request data structures are used to make requests to the block devices in the system. The requests are always to read or write blocks of data to or from the buffer cache.
(*)rtable -> Each rtable data structure holds information about the route to take in order to send packets to an IP host. rtable data structures are used within the IP route cache.
(*)semaphore -> Semaphores are used to protect critical data structures and regions of code.
(*)sk_buff -> The sk_buff data structure is used to describe network data as it moves between the layers of protocol.
(*)sock or socket -> Each sock data structure holds protocol specific information about a BSD socket.
(*)task_struct -> Each task_struct data structure describes a process or task in the system.
(*)tq_struct -> Each task queue (tq_struct) data structure holds information about work that has been queued. This is usually a task needed by a device driver but which does not have to be done immediately.
(*)vm_area_struct -> Each vm_area_struct data structure describes an area of virtual memory for a process.
