that buffer resides in

arm_dma_map_page - map a portion of a page for streaming DMA : valid struct device pointer, or NULL for ISA and EISA-like devices

: offset into page for start of buffer : size of buffer to map

dma_map_page - map a portion of a page for streaming DMA : valid struct device pointer, or NULL for ISA and EISA-like devices

: offset into page for start of buffer : size of buffer to map

blk_add_request_payload - add a payload to a request : request to update

: length of the payload.

This allows to later add a payload to an already submitted request by a block driver. The driver needs to take care of freeing the payload itself.

Note that this is a quite horrible hack and nothing but handling of discard requests should ever use it.

blkdev_issue_write_same - queue a write same operation : target blockdev : start sector : number of sectors to write : memory allocation flags (for bio_alloc)

Description: Issue a write same request for the sectors in question.

ata_read_log_page - read a specific log page : target device : log to read

: buffer to store read page : number of sectors to read

Read log page using READ_LOG_EXT command.

LOCKING: Kernel thread context (may sleep).

RETURNS: 0 on success, AC_ERR_* mask otherwise.

calc_block_sector - Calculate blocks, pages and ofs.

: offset in flash : first plane block index calculated : second plane block index calculated

: offset in page : 0 if docg3 in normal mode, 1 if docg3 in fast mode, 2 if docg3 in reliable mode.

The calculation is based on the reliable/normal mode. In normal mode, the 64 pages of a block are available. In reliable mode, as pages 2*n and 2*n+1 are clones, only 32 pages per block are available.

nand_read_page_raw - [INTERN] read raw page data without ecc : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

Not for syndrome calculating ECC controllers, which use a special oob layout.

nand_read_page_raw_syndrome - [INTERN] read raw page data without ecc : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

We need a special oob layout and handling even when OOB isn't used.

nand_read_page_swecc - [REPLACEABLE] software ECC based page read function : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

nand_read_page_hwecc - [REPLACEABLE] hardware ECC based page read function : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

Not for syndrome calculating ECC controllers which need a special oob layout.

nand_read_page_hwecc_oob_first - [REPLACEABLE] hw ecc, read oob first : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

Hardware ECC for large page chips, require OOB to be read first. For this ECC mode, the write_page method is re-used from ECC_HW. These methods read/write ECC from the OOB area, unlike the ECC_HW_SYNDROME support with multiple ECC steps, follows the "infix ECC" scheme and reads/writes ECC from the data area, by overwriting the NAND manufacturer bad block markings.

nand_read_page_syndrome - [REPLACEABLE] hardware ECC syndrome based page read : mtd info structure : nand chip info structure : buffer to store read data : caller requires OOB data read to chip->oob_poi

The hw generator calculates the error syndrome automatically. Therefore we need a special oob layout and handling.

nand_read_oob_std - [REPLACEABLE] the most common OOB data read function : mtd info structure : nand chip info structure

nand_read_oob_syndrome - [REPLACEABLE] OOB data read function for HW ECC with syndromes : mtd info structure : nand chip info structure

nand_write_oob_std - [REPLACEABLE] the most common OOB data write function : mtd info structure : nand chip info structure

nand_write_oob_syndrome - [REPLACEABLE] OOB data write function for HW ECC with syndrome - only for large page flash : mtd info structure : nand chip info structure

nand_write_page - [REPLACEABLE] write one page : MTD device structure : NAND chip descriptor : the data to write : must write chip->oob_poi to OOB

: cached programming : use _raw version of write_page

e1000_set_page_igp - Set page as on IGP-like PHY(s) : pointer to the HW structure

Sets PHY page required for PHY register access. Assumes semaphore is already acquired. Note, this function sets phy.addr to 1 so the caller must set it appropriately (if necessary) after this function returns.

e1000_get_phy_addr_for_bm_page - Retrieve PHY page address

Returns the phy address for the page requested.

e1000_get_phy_addr_for_hv_page - Get PHY address based on page

This function determines if the specified inquiry page is supported.

Return value: 1 if page is supported / 0 if not

bio_integrity_add_page - Attach integrity metadata : bio to update

: number of bytes of integrity metadata in page : start offset within page

Description: Attach a page containing integrity metadata to bio.

bio_add_pc_page - attempt to add page to bio : the target queue : destination bio

: vec entry length : vec entry offset

Attempt to add a page to the bio_vec maplist. This can fail for a number of reasons, such as the bio being full or target block device limitations. The target block device must allow bio's up to PAGE_SIZE, so it is always possible to add a single page to an empty bio.

This should only be used by REQ_PC bios.

bio_add_page - attempt to add page to bio : destination bio

: vec entry length : vec entry offset

Attempt to add a page to the bio_vec maplist. This can fail for a number of reasons, such as the bio being full or target block device limitations. The target block device must allow bio's up to PAGE_SIZE, so it is always possible to add a single page to an empty bio.

Description: vxfs_immed_readpage reads a part of the immed area of the file that hosts into the pagecache.

Returns: Zero on success, else a negative error code.

Locking status:

Description: The vxfs_readpage routine reads

void journal_invalidatepage() - invalidate a journal page : journal to use for flush

: length of page to invalidate.

Reap page buffers containing data after offset in page.

void jbd2_journal_invalidatepage() : journal to use for flush...

: length of page to invalidate.

Reap page buffers containing data after offset in page.

nfs_create_request - Create an NFS read/write request. : open context to use : inode to which the request is attached

: starting offset within the page for the write : number of bytes to read/write

The page must be locked by the caller. This makes sure we never create two different requests for the same page. User should ensure it is safe to sleep in this function.

nilfs_page_buffers_clean - check if a page has dirty buffers or not.

nilfs_page_buffers_clean() returns zero if the page has dirty buffers. Otherwise, it returns non-zero value.

Fill the page

For non-resident attributes, ntfs_readpage() fills the

: index inode containing the described by this context : index entry (points into or ) : index entry data (points into ) : length in bytes of : 'true' if is in and 'false' if it is in : index root if and NULL otherwise : attribute search context if and NULL otherwise : base inode if and NULL otherwise : index block if is 'false' and NULL otherwise

is the index inode this context belongs to.

is the index entry described by this context. and are the index entry data and its length in bytes, respectively. simply points into . This is probably what the user is interested in.

If is 'true', is in the index root attribute described by the attribute search context and the base inode . and

allocate_budget - allocate budget for 'ubifs_write_begin()'. : UBIFS file-system description object

: UBIFS inode object the page belongs to : non-zero if the page is appended

This is a helper function for 'ubifs_write_begin()' which allocates budget for the operation. The budget is allocated differently depending on whether this is appending, whether the page is dirty or not, and so on. This function leaves the ->ui_mutex locked in case of appending. Returns zero in case of success and %-ENOSPC in case of failure.

cancel_budget - cancel budget. : UBIFS file-system description object

: UBIFS inode object the page belongs to : non-zero if the page is appended

This is a helper function for a page write operation. It unlocks the ->ui_mutex in case of appending.

populate_page - copy data nodes into a page for bulk-read. : UBIFS file-system description object

: bulk-read information
: next zbranch slot

This function returns %0 on success and a negative error code on failure.

ubifs_bulk_read - determine whether to bulk-read and, if so, do it.

Some flash media are capable of reading sequentially at faster rates. UBIFS bulk-read facility is designed to take advantage of that, by reading in one go consecutive data nodes that are also located consecutively in the same LEB. This function returns %1 if a bulk-read is done and %0 otherwise.

submit - submit BIO request. : READ or WRITE. physical offset of page.

: list of pending biod (for async reading)

Straight from the textbook - allocate and initialize the bio. If we're reading, make sure the page is marked as dirty. Then submit it and, if == NULL, wait.

add_to_page_cache_locked - add a locked page to the pagecache

: the page's address_space : page index : page allocation mode

This function is used to add a page to the pagecache. It must be locked. This function does not add the page to the LRU. The caller must do that.

soft_offline_page - Soft offline a page.

: flags. Same as memory_failure().

Returns 0 on success, otherwise negated errno.

Soft offline a page, by migration or invalidation, without killing anything. This is for the case when a page is not corrupted yet (so it's still valid to access), but has had a number of corrected errors and is better taken out.

The actual policy on when to do that is maintained by user space.

This should never impact any application or cause data loss, however it might take some time.

This is not a 100% solution for all memory, but tries to be ``good enough'' for the majority of memory.

page_remove_rmap - take down pte mapping from a page

The caller needs to hold the pte lock.

deactivate_page - forcefully deactivate a page

This function hints the VM that

add_to_swap - allocate swap space for a page

Allocate swap space for the page and add the page to the swap cache. Caller needs to hold the page lock.

putback_lru_page - put previously isolated page onto appropriate LRU list

Add previously isolated

isolate_lru_page - tries to isolate a page from its LRU list

Isolates a