<P> Device drivers and kernel extensions run in kernel space (ring 0 in many CPU architectures), with full access to the hardware, although some exceptions run in user space, for example filesystems based on FUSE / CUSE, and parts of UIO . The graphics system most people use with Linux does not run within the kernel . Unlike standard monolithic kernels, device drivers are easily configured as modules, and loaded or unloaded while the system is running . Also, unlike standard monolithic kernels, device drivers can be pre-empted under certain conditions; this feature was added to handle hardware interrupts correctly, and to better support symmetric multiprocessing . By choice, the Linux kernel has no binary kernel interface . </P> <P> The hardware is also incorporated into the file hierarchy . Device drivers interface to user applications via an entry in the / dev or / sys directories . Process information as well is mapped to the file system through the / proc directory . </P> <Table> Various layers within Linux, also showing separation between the userland and kernel space <Tr> <Th> User mode </Th> <Td_colspan="1"> User applications </Td> <Td_colspan="5"> For example, bash, LibreOffice, GIMP, Blender, 0 A.D., Mozilla Firefox, etc . </Td> </Tr> <Tr> <Td> Low - level system components: </Td> <Td_colspan="1"> System daemons: systemd, runit, logind, networkd, PulseAudio,...</Td> <Td_colspan="1"> Windowing system: X11, Wayland, Mir, SurfaceFlinger (Android) </Td> <Td_colspan="2"> Other libraries: GTK+, Qt, EFL, SDL, SFML, FLTK, GNUstep, etc . </Td> <Td_colspan="1"> Graphics: Mesa, AMD Catalyst,...</Td> </Tr> <Tr> <Td_colspan="1"> C standard library </Td> <Td_colspan="5"> open (), exec (), sbrk (), socket (), fopen (), calloc (),...(up to 2000 subroutines) glibc aims to be POSIX / SUS - compatible, uClibc targets embedded systems, bionic written for Android, etc . </Td> </Tr> <Tr> <Th> Kernel mode </Th> <Td> Linux kernel </Td> <Td_colspan="5"> stat, splice, dup, read, open, ioctl, write, mmap, close, exit, etc. (about 380 system calls) The Linux kernel System Call Interface (SCI, aims to be POSIX / SUS - compatible) </Td> </Tr> <Tr> <Td> Process scheduling subsystem </Td> <Td> IPC subsystem </Td> <Td> Memory management subsystem </Td> <Td> Virtual files subsystem </Td> <Td> Network subsystem </Td> </Tr> <Tr> <Td_colspan="5"> Other components: ALSA, DRI, evdev, LVM, device mapper, Linux Network Scheduler, Netfilter Linux Security Modules: SELinux, TOMOYO, AppArmor, Smack </Td> </Tr> <Tr> <Th_colspan="7"> Hardware (CPU, main memory, data storage devices, etc .) </Th> </Tr> </Table> <Tr> <Th> User mode </Th> <Td_colspan="1"> User applications </Td> <Td_colspan="5"> For example, bash, LibreOffice, GIMP, Blender, 0 A.D., Mozilla Firefox, etc . </Td> </Tr>

Which version of the linux kernal does android rely upon
find me the text answering this question