I have been through the answer of this question but do not quite understand the difference between system calls and library functions. Conceptually, what is the difference between the two?
Difference between system calls and library functions
Architecturelibrariessystem-calls
Related Question
- Linux – FreeBSD and GNU/Linux system calls compatibility library
- Linux – How Are System Calls from Man 2 Invoked?
- Is the vdso shared library (linux-vdso.so) the library that contains the kernel object code (system calls)
- In what library on Linux are the system calls and how is this library linked to the executable object file that contains the system calls
Best Answer
Conceptually, a library function is part of your process.
At run-time, your executable code and the code of any libraries (such as libc.so) it depends on, get linked into a single process. So, when you call a function in such a library, it executes as part of your process, with the same resources and privileges. It's the same idea as calling a function you wrote yourself (with possible exceptions like PLT and/or trampoline functions, which you can look up if you care).
Conceptually, a system call is a special interface used to make a call from your code (which is generally unprivileged) to the kernel (which has the right to escalate privileges as necessary).
For example, see the Linux man brk. When a C program calls
malloc
to allocate memory, it is calling a library function in glibc.If there is already enough space for the allocation inside the process, it can do any necessary heap management and return the memory to the caller.
If not, glibc needs to request more memory from the kernel: it (probably) calls the
brk
glibc function, which in turn calls thebrk
syscall. Only once control has passed to the kernel, via the syscall, can the global virtual memory state be modified to reserve more memory, and map it into your process' address space.