Different events, and scenarios require different types of information. More...

Public Attributes
std::vector< uint8_t >	buffer

uint32_t	size

uint64_t	offset

uint32_t	filePointer

uint32_t	lunID

Detailed Description

Different events, and scenarios require different types of information.

Keep in mind that for a read-from-disk transaction the host at first a datastructure fetches to determine where and what the command is, then the command fetches and the structure fetches to determine where the different read transactions should be placed and then transfers all the read fragments. It then answers to the original caller with two replies, one for the command, and one for UFS. Each of these stages trigger a different event, and each event needs to know what happened in the previous stage and what is going to happen in the current one. This happens also for writes, SCSI maintanance, UFS maintanance, command management and task management. Transfer information. @filePointer this does not point to a file, but to a position on the disk image (which is from the software systems perspective a position in a file)

Definition at line 439 of file ufs_device.hh.