Query: ll_rw_block
OS: suse
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
LL_RW_BLOCK(9) The Linux VFS LL_RW_BLOCK(9)NAMEll_rw_block - level access to block devices (DEPRECATED)SYNOPSISvoid ll_rw_block(int rw, int nr, struct buffer_head * bhs[]);ARGUMENTSrw whether to READ or WRITE or SWRITE or maybe READA (readahead) nr number of struct buffer_heads in the array bhs[] array of pointers to struct buffer_headDESCRIPTIONll_rw_block takes an array of pointers to struct buffer_heads, and requests an I/O operation on them, either a READ or a WRITE. The third SWRITE is like WRITE only we make sure that the *current* data in buffers are sent to disk. The fourth READA option is described in the documentation for generic_make_request which ll_rw_block calls. This function drops any buffer that it cannot get a lock on (with the BH_Lock state bit) unless SWRITE is required, any buffer that appears to be clean when doing a write request, and any buffer that appears to be up-to-date when doing read request. Further it marks as clean buffers that are processed for writing (the buffer cache won't assume that they are actually clean until the buffer gets unlocked). ll_rw_block sets b_end_io to simple completion handler that marks the buffer up-to-date (if approriate), unlocks the buffer and wakes any waiters. All of the buffers must be for the same device, and must also be a multiple of the current approved size for the device.COPYRIGHTKernel Hackers Manual 2.6. July 2010 LL_RW_BLOCK(9)
Related Man Pages |
---|
ll_rw_block(9) - suse |
journal_get_undo_access(9) - centos |
rdma_reg_write(3) - centos |
struct_journal_s(9) - suse |
buf(9) - hpux |
Similar Topics in the Unix Linux Community |
---|
Permissions - passing a file as the argument |
Problem Please help... |
Input buffer and READ |