Linux kernel interfaces: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 16: replaced (1×) / removed (2×) deprecated |dead-url= and |deadurl= with |url-status=;
m Replaces obsolete tag.
Line 107:
* [[Semaphore (programming)]]
* [[system call]]{{snd}} is a function to facilitate programs to request services from the kernel
** <tt>{{mono|[[File descriptor|eventfd()]]</tt> }}
** [[netlink]]{{snd}} socket family used for IPC between kernel and user space processes, designed as the successor of <tt>{{mono|[[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