Linux kernel interfaces: Difference between revisions

Content deleted Content added
No edit summary
Tags: Visual edit Mobile edit Mobile web edit
No edit summary
Tags: Visual edit Mobile edit Mobile web edit
Line 82:
== See also ==
{{Portal|Linux}}
* ''[[The Linux Programming Interface]]'' by [[Michael Kerrisk]]
* [[Semaphore (programming)]]
* [[system call]]{{snd}} is a function to facilitate programs to request services from the kernel
** <tt>[[File descriptor|eventfd()]]</tt>
** [[netlink]]{{snd}} socket family used for IPC between kernel and user space processes, designed as the successor of <tt>[[ioctl]]</tt>; Netlink was added by [[Alan Cox]] during Linux kernel 1.3 development as a character driver interface to provide multiple kernel and user-space bidirectional communications links. Then, Alexey Kuznetsov extended it during Linux kernel 2.1 development to provide a flexible and extensible messaging interface to the new advanced routing infrastructure. Since then, Netlink sockets have become one of the main interfaces that kernel subsystems provide to user-space applications in Linux. Modern [[Wireless network interface controller|WNIC]] [[Comparison of open-source wireless drivers|drivers]] use it to communicate with user-space.
* [[Windows API]]{{snd}} article on various API available on Microsoft Windows operating systems
** [[windows.h]]{{snd}} header file for the [[C (programming language)|C programming language]] which contains declarations for ''all'' of the functions in the Windows API
* [[Wine (software)|Wine]]{{snd}} a compatibility layer between Linux and programs written for Microsoft Windows
* [[Hybrislinguistic (software)|libhybris]]is – compatibility layer between Linux and programs written for Android
 
== References ==