I'm reading source code of the linux tool badblocks. They use the read() function there. Is there a difference to the standard C fread() function? (I'm not counting the arguments as a difference.)
What is the difference between read() and fread()?
Viewed 66821
6 Answers
read() is a low level, unbuffered read. It makes a direct system call on UNIX.
fread() is part of the C library, and provides buffered reads. It is usually implemented by calling read() in order to fill its buffer.
Family read() -> open, close, read, write
Family fread() -> fopen, fclose, fread, fwrite
Family read:
- are system calls
- are not formatted IO: we have a non formatted byte stream
Family fread
- are functions of the standard C library (libc)
- use an internal buffer
- are formatted IO (with the "%.." parameter) for some of them
- use always the Linux buffer cache
More details here, although note that this post contains some incorrect information.
As I remember it the read() level APIs do not do buffering - so if you read() 1 byte at a time you will have a huge perf penalty compared to doing the same thing with fread(). fread() will pull a block and dole it out as you ask for it. read() will drop to the kernel for each call.
read() --> Directly using this system call to kernel and that performs the IO operation.
fread() --> Is a function provided in standard library.
Calling fread() is mainly used for binary file data where struct data are stored.
The main difference between these two is the number of system calls in your application.
The fread() kind of standard IO library functions are optimized for system calls, rather your application making system calls.
Related