Changes between Version 13 and Version 14 of ioc_device_api

Timestamp:

Jan 21, 2020, 9:04:43 PM (5 years ago)

Author:

alain

Comment:

--

ioc_device_api

@@ -9 +9 @@
 The block size is supposed to be 512 bytes.
 
-It supports a first ''user'' API, used by the user-level system calls, implementing four operation types : the '''IOC_READ''', '''IOC_WRITE''', '''IOC_SYNC_READ''', and '''IOC_SYNC_WRITE''' operations move a given number of contiguous blocks between the block device and a kernel memory buffer. This API is detailed in section C below.
+The ''user'' API contains the functions used by the user-level system calls, and defines four operation types : the '''IOC_READ''', '''IOC_WRITE''', '''IOC_SYNC_READ''', and '''IOC_SYNC_WRITE''' operations move a given number of contiguous blocks between the block device and a kernel memory buffer. This API is detailed in section C below.
 
 * The '''asynchronous''' READ and WRITE operations are not directly executed by the client thread. The READ and WRITE requests are registered in the waiting queue rooted in the IOC chdev descriptor. These requests are actually handled by a dedicated server thread running in the cluster containing the chdev descriptor, that call the ''ioc_driver_cmd()'' function.
@@ -70 +70 @@
 * void '''ioc_driver_isr'''( chdev_t * ioc_chdev )
 
-The ioc_driver_cmd()'' function arguments are actually defined in the ''ioc_command_t'' structure embedded in the client thread descriptor. One command contains four informations:
+The ''ioc_driver_cmd()'' function arguments are actually defined in the ''ioc_command_t'' structure embedded in the client thread descriptor. One command contains four informations:
  - '''type''' : operation type (defined below)
  - '''count''' : number of contiguous blocks to be moved.