8287fa5fb4
The reason this bounce buffer exists is to allow code
reuse between rd_mcp and fileio in DIF mode. But the fact is,
that this bounce is really not needed at all, we can simply call
sbc_dif_verify on cmd->t_prot_sg and use it for file IO.
This also removes fd_do_prot_rw as fd_do_rw was generalised
to receive file pointer, block size (8 bytes for DIF data) and
total data length.
(Fix apply breakage from commit c836777 - nab)
Tested-by: Akinobu Mita <akinobu.mita@gmail.com>
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
48 lines
1.1 KiB
C
48 lines
1.1 KiB
C
#ifndef TARGET_CORE_FILE_H
|
|
#define TARGET_CORE_FILE_H
|
|
|
|
#define FD_VERSION "4.0"
|
|
|
|
#define FD_MAX_DEV_NAME 256
|
|
#define FD_MAX_DEV_PROT_NAME FD_MAX_DEV_NAME + 16
|
|
#define FD_DEVICE_QUEUE_DEPTH 32
|
|
#define FD_MAX_DEVICE_QUEUE_DEPTH 128
|
|
#define FD_BLOCKSIZE 512
|
|
/*
|
|
* Limited by the number of iovecs (2048) per vfs_[writev,readv] call
|
|
*/
|
|
#define FD_MAX_BYTES 8388608
|
|
|
|
#define RRF_EMULATE_CDB 0x01
|
|
#define RRF_GOT_LBA 0x02
|
|
|
|
#define FBDF_HAS_PATH 0x01
|
|
#define FBDF_HAS_SIZE 0x02
|
|
#define FDBD_HAS_BUFFERED_IO_WCE 0x04
|
|
#define FDBD_FORMAT_UNIT_SIZE 2048
|
|
|
|
struct fd_dev {
|
|
struct se_device dev;
|
|
|
|
u32 fbd_flags;
|
|
unsigned char fd_dev_name[FD_MAX_DEV_NAME];
|
|
/* Unique Ramdisk Device ID in Ramdisk HBA */
|
|
u32 fd_dev_id;
|
|
/* Number of SG tables in sg_table_array */
|
|
u32 fd_table_count;
|
|
u32 fd_queue_depth;
|
|
u32 fd_block_size;
|
|
unsigned long long fd_dev_size;
|
|
struct file *fd_file;
|
|
struct file *fd_prot_file;
|
|
/* FILEIO HBA device is connected to */
|
|
struct fd_host *fd_host;
|
|
} ____cacheline_aligned;
|
|
|
|
struct fd_host {
|
|
u32 fd_host_dev_id_count;
|
|
/* Unique FILEIO Host ID */
|
|
u32 fd_host_id;
|
|
} ____cacheline_aligned;
|
|
|
|
#endif /* TARGET_CORE_FILE_H */
|