内存与io访问（Memory and IO access）.docVIP

内存与io访问（Memory and IO access） Memory and I/O access Memory allocation The kernel provides a unified memory management interface for device drivers, so there is no need for issues such as segmentation and paging. The application memory for memory in the Linux kernel space includes kmalloc (), __get_free_pages (), and vmalloc (). Kmalloc __get_free_pages and () () the application of memory in physical memory mapping area, and on the physical is continuous, they and the real physical addresses only a fixed offset, so there is a simple transformation relationship. And vmalloc () in the virtual memory space is given a piece of contiguous memory space, in essence, the continuous presence in the physical memory in the virtual must not continuous, and vmalloc () the application of virtual memory, and also does not have the simple conversion relations between physical memory. Kmalloc function inside Kmalloc is a powerful and fast (unless blocked) tool that is allocated to the existing physical memory and maintains the original data (not clear). Prototype: # include Linux/slab. H Void * kmalloc (size_t size, int flags); The size parameter The kernel manages the physical memory of the system, and the physical memory can only be allocated according to the page. Kmalloc and typical user space malloc are actually quite different, and the kernel USES special based allocation techniques to best use system RAM. It is important to note that the kernel can only assign a number of predefined, fixed-size byte arrays. The smallest chunk of memory that kmalloc can handle is 32 or 64 bytes (architecture dependent), and the upper limit of the memory block size varies with the system and kernel configuration. In view of portability, memory should not be greater than 128 KB. If you need more than a few kilobytes of memory, youd better use other methods. The flags parameter The memory allocation always ends up calling __get_free_pages for the actual allocation, which is where the GFP_ prefix