Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:fs\buffer.c Create Date:2022-07-28 20:14:13
Last Modify:2020-03-18 10:38:29 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:ll_rw_block: low-level access to block devices (DEPRECATED)*@op: whether to %READ or %WRITE*@op_flags: req_flag_bits*@nr: number of &struct buffer_heads in the array*@bhs: array of pointers to &struct buffer_head* ll_rw_block() takes an array of pointers

Proto:void ll_rw_block(int op, int op_flags, int nr, struct buffer_head *bhs[])

Type:void

Parameter:

TypeParameterName
intop
intop_flags
intnr
struct buffer_head *bhs
3152  When i < nr cycle
3153  bh = bhs[i]
3155  If Not trylock_buffer(bh) Then Continue
3157  If op == WRITE Then
3158  If test_clear_buffer_dirty(bh) Then
3159  I/O completion = end_buffer_write_sync
3160  get_bh(bh)
3161  submit_bh(op, op_flags, bh)
3162  Continue
3164  Else
3165  If Not Emit the buffer bitops functions. Note that there are also functions* of the form "mark_buffer_foo()". These are higher-level functions which* do something in addition to setting a b_state bit. Then
3172  unlock_buffer(bh)
Caller
NameDescribe
write_boundary_blockCalled when we've recently written block `bblock', and it is known that* `bblock' was for a buffer_boundary() buffer. This means that the block at* `bblock + 1' is probably a dirty indirect block. Hunt it down and, if it's* dirty, schedule it for IO
__breadaheadDo async read-ahead on a buffer..
__block_write_begin_int
block_truncate_page