Linux Interrupt Understanding

1, the process, the thread is only for the application layer, and the kernel call, the driver does not have this concept, the call is the kernel call in the same function or variable, so application layer multiple applications operate the same hardware, especially to add the mutex operation, 8250 through the CS pin to determine which serial port to send data

2, send, receive the resolution of the concurrency operation, mainly to prevent repeated calls to the function, wait for the function of the hardware has not yet finished operation to allow the call, receive the general to add mutually exclusive operation, and can receive why did not join the mutex operation?

3, ring buffer, only one write a read, is not required to lock operation

4, the function of the underlying hardware if there are multiple places to be called, generally to join the lock mechanism

Linux Interrupt Understanding