You've already forked linux-apfs
mirror of
https://github.com/linux-apfs/linux-apfs.git
synced 2026-05-01 15:00:59 -07:00
[PATCH] DocBook: fix some descriptions
Some KernelDoc descriptions are updated to match the current code. No code changes. Signed-off-by: Martin Waitz <tali@admingilde.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
committed by
Linus Torvalds
parent
6013d5445f
commit
67be2dd1ba
@@ -140,6 +140,7 @@ inline void bio_init(struct bio *bio)
|
||||
* bio_alloc_bioset - allocate a bio for I/O
|
||||
* @gfp_mask: the GFP_ mask given to the slab allocator
|
||||
* @nr_iovecs: number of iovecs to pre-allocate
|
||||
* @bs: the bio_set to allocate from
|
||||
*
|
||||
* Description:
|
||||
* bio_alloc_bioset will first try it's on mempool to satisfy the allocation.
|
||||
@@ -629,6 +630,7 @@ out:
|
||||
|
||||
/**
|
||||
* bio_map_user - map user address into bio
|
||||
* @q: the request_queue_t for the bio
|
||||
* @bdev: destination block device
|
||||
* @uaddr: start of user address
|
||||
* @len: length in bytes
|
||||
|
||||
+6
-5
@@ -774,15 +774,14 @@ repeat:
|
||||
/**
|
||||
* sync_mapping_buffers - write out and wait upon a mapping's "associated"
|
||||
* buffers
|
||||
* @buffer_mapping - the mapping which backs the buffers' data
|
||||
* @mapping - the mapping which wants those buffers written
|
||||
* @mapping: the mapping which wants those buffers written
|
||||
*
|
||||
* Starts I/O against the buffers at mapping->private_list, and waits upon
|
||||
* that I/O.
|
||||
*
|
||||
* Basically, this is a convenience function for fsync(). @buffer_mapping is
|
||||
* the blockdev which "owns" the buffers and @mapping is a file or directory
|
||||
* which needs those buffers to be written for a successful fsync().
|
||||
* Basically, this is a convenience function for fsync().
|
||||
* @mapping is a file or directory which needs those buffers to be written for
|
||||
* a successful fsync().
|
||||
*/
|
||||
int sync_mapping_buffers(struct address_space *mapping)
|
||||
{
|
||||
@@ -1263,6 +1262,7 @@ __getblk_slow(struct block_device *bdev, sector_t block, int size)
|
||||
|
||||
/**
|
||||
* mark_buffer_dirty - mark a buffer_head as needing writeout
|
||||
* @bh: the buffer_head to mark dirty
|
||||
*
|
||||
* mark_buffer_dirty() will set the dirty bit against the buffer, then set its
|
||||
* backing page dirty, then tag the page as dirty in its address_space's radix
|
||||
@@ -1501,6 +1501,7 @@ EXPORT_SYMBOL(__breadahead);
|
||||
|
||||
/**
|
||||
* __bread() - reads a specified block and returns the bh
|
||||
* @bdev: the block_device to read from
|
||||
* @block: number of block
|
||||
* @size: size (in bytes) to read
|
||||
*
|
||||
|
||||
+3
-1
@@ -512,7 +512,8 @@ restart:
|
||||
}
|
||||
|
||||
/**
|
||||
* sync_inodes
|
||||
* sync_inodes - writes all inodes to disk
|
||||
* @wait: wait for completion
|
||||
*
|
||||
* sync_inodes() goes through each super block's dirty inode list, writes the
|
||||
* inodes out, waits on the writeout and puts the inodes back on the normal
|
||||
@@ -604,6 +605,7 @@ EXPORT_SYMBOL(sync_inode);
|
||||
/**
|
||||
* generic_osync_inode - flush all dirty data for a given inode to disk
|
||||
* @inode: inode to write
|
||||
* @mapping: the address_space that should be flushed
|
||||
* @what: what to write and wait upon
|
||||
*
|
||||
* This can be called by file_write functions for files which have the
|
||||
|
||||
+46
-46
@@ -160,52 +160,6 @@ map_buffer_to_page(struct page *page, struct buffer_head *bh, int page_block)
|
||||
} while (page_bh != head);
|
||||
}
|
||||
|
||||
/**
|
||||
* mpage_readpages - populate an address space with some pages, and
|
||||
* start reads against them.
|
||||
*
|
||||
* @mapping: the address_space
|
||||
* @pages: The address of a list_head which contains the target pages. These
|
||||
* pages have their ->index populated and are otherwise uninitialised.
|
||||
*
|
||||
* The page at @pages->prev has the lowest file offset, and reads should be
|
||||
* issued in @pages->prev to @pages->next order.
|
||||
*
|
||||
* @nr_pages: The number of pages at *@pages
|
||||
* @get_block: The filesystem's block mapper function.
|
||||
*
|
||||
* This function walks the pages and the blocks within each page, building and
|
||||
* emitting large BIOs.
|
||||
*
|
||||
* If anything unusual happens, such as:
|
||||
*
|
||||
* - encountering a page which has buffers
|
||||
* - encountering a page which has a non-hole after a hole
|
||||
* - encountering a page with non-contiguous blocks
|
||||
*
|
||||
* then this code just gives up and calls the buffer_head-based read function.
|
||||
* It does handle a page which has holes at the end - that is a common case:
|
||||
* the end-of-file on blocksize < PAGE_CACHE_SIZE setups.
|
||||
*
|
||||
* BH_Boundary explanation:
|
||||
*
|
||||
* There is a problem. The mpage read code assembles several pages, gets all
|
||||
* their disk mappings, and then submits them all. That's fine, but obtaining
|
||||
* the disk mappings may require I/O. Reads of indirect blocks, for example.
|
||||
*
|
||||
* So an mpage read of the first 16 blocks of an ext2 file will cause I/O to be
|
||||
* submitted in the following order:
|
||||
* 12 0 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16
|
||||
* because the indirect block has to be read to get the mappings of blocks
|
||||
* 13,14,15,16. Obviously, this impacts performance.
|
||||
*
|
||||
* So what we do it to allow the filesystem's get_block() function to set
|
||||
* BH_Boundary when it maps block 11. BH_Boundary says: mapping of the block
|
||||
* after this one will require I/O against a block which is probably close to
|
||||
* this one. So you should push what I/O you have currently accumulated.
|
||||
*
|
||||
* This all causes the disk requests to be issued in the correct order.
|
||||
*/
|
||||
static struct bio *
|
||||
do_mpage_readpage(struct bio *bio, struct page *page, unsigned nr_pages,
|
||||
sector_t *last_block_in_bio, get_block_t get_block)
|
||||
@@ -320,6 +274,52 @@ confused:
|
||||
goto out;
|
||||
}
|
||||
|
||||
/**
|
||||
* mpage_readpages - populate an address space with some pages, and
|
||||
* start reads against them.
|
||||
*
|
||||
* @mapping: the address_space
|
||||
* @pages: The address of a list_head which contains the target pages. These
|
||||
* pages have their ->index populated and are otherwise uninitialised.
|
||||
*
|
||||
* The page at @pages->prev has the lowest file offset, and reads should be
|
||||
* issued in @pages->prev to @pages->next order.
|
||||
*
|
||||
* @nr_pages: The number of pages at *@pages
|
||||
* @get_block: The filesystem's block mapper function.
|
||||
*
|
||||
* This function walks the pages and the blocks within each page, building and
|
||||
* emitting large BIOs.
|
||||
*
|
||||
* If anything unusual happens, such as:
|
||||
*
|
||||
* - encountering a page which has buffers
|
||||
* - encountering a page which has a non-hole after a hole
|
||||
* - encountering a page with non-contiguous blocks
|
||||
*
|
||||
* then this code just gives up and calls the buffer_head-based read function.
|
||||
* It does handle a page which has holes at the end - that is a common case:
|
||||
* the end-of-file on blocksize < PAGE_CACHE_SIZE setups.
|
||||
*
|
||||
* BH_Boundary explanation:
|
||||
*
|
||||
* There is a problem. The mpage read code assembles several pages, gets all
|
||||
* their disk mappings, and then submits them all. That's fine, but obtaining
|
||||
* the disk mappings may require I/O. Reads of indirect blocks, for example.
|
||||
*
|
||||
* So an mpage read of the first 16 blocks of an ext2 file will cause I/O to be
|
||||
* submitted in the following order:
|
||||
* 12 0 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16
|
||||
* because the indirect block has to be read to get the mappings of blocks
|
||||
* 13,14,15,16. Obviously, this impacts performance.
|
||||
*
|
||||
* So what we do it to allow the filesystem's get_block() function to set
|
||||
* BH_Boundary when it maps block 11. BH_Boundary says: mapping of the block
|
||||
* after this one will require I/O against a block which is probably close to
|
||||
* this one. So you should push what I/O you have currently accumulated.
|
||||
*
|
||||
* This all causes the disk requests to be issued in the correct order.
|
||||
*/
|
||||
int
|
||||
mpage_readpages(struct address_space *mapping, struct list_head *pages,
|
||||
unsigned nr_pages, get_block_t get_block)
|
||||
|
||||
+1
-1
@@ -1742,7 +1742,7 @@ struct dentry *proc_pid_unhash(struct task_struct *p)
|
||||
|
||||
/**
|
||||
* proc_pid_flush - recover memory used by stale /proc/@pid/x entries
|
||||
* @proc_entry: directoy to prune.
|
||||
* @proc_dentry: directoy to prune.
|
||||
*
|
||||
* Shrink the /proc directory that was used by the just killed thread.
|
||||
*/
|
||||
|
||||
+7
-2
@@ -51,7 +51,10 @@ EXPORT_SYMBOL(seq_open);
|
||||
|
||||
/**
|
||||
* seq_read - ->read() method for sequential files.
|
||||
* @file, @buf, @size, @ppos: see file_operations method
|
||||
* @file: the file to read from
|
||||
* @buf: the buffer to read to
|
||||
* @size: the maximum number of bytes to read
|
||||
* @ppos: the current position in the file
|
||||
*
|
||||
* Ready-made ->f_op->read()
|
||||
*/
|
||||
@@ -219,7 +222,9 @@ Eoverflow:
|
||||
|
||||
/**
|
||||
* seq_lseek - ->llseek() method for sequential files.
|
||||
* @file, @offset, @origin: see file_operations method
|
||||
* @file: the file in question
|
||||
* @offset: new position
|
||||
* @origin: 0 for absolute, 1 for relative position
|
||||
*
|
||||
* Ready-made ->f_op->llseek()
|
||||
*/
|
||||
|
||||
+2
-2
@@ -96,7 +96,7 @@ static int fill_read_buffer(struct dentry * dentry, struct sysfs_buffer * buffer
|
||||
/**
|
||||
* flush_read_buffer - push buffer to userspace.
|
||||
* @buffer: data buffer for file.
|
||||
* @userbuf: user-passed buffer.
|
||||
* @buf: user-passed buffer.
|
||||
* @count: number of bytes requested.
|
||||
* @ppos: file position.
|
||||
*
|
||||
@@ -164,7 +164,7 @@ out:
|
||||
/**
|
||||
* fill_write_buffer - copy buffer from userspace.
|
||||
* @buffer: data buffer for file.
|
||||
* @userbuf: data from user.
|
||||
* @buf: data from user.
|
||||
* @count: number of bytes in @userbuf.
|
||||
*
|
||||
* Allocate @buffer->page if it hasn't been already, then
|
||||
|
||||
Reference in New Issue
Block a user