diff options
| author | Roland Dreier <roland@purestorage.com> | 2012-02-14 01:18:17 +0100 |
|---|---|---|
| committer | Nicholas Bellinger <nab@linux-iscsi.org> | 2012-02-25 23:37:49 +0100 |
| commit | 015487b89f27d91d95a056cdc3c85e6c729bff12 (patch) | |
| tree | 0cecb2acc903154e25abb23e8f345f301fcd1ef5 /drivers/target/loopback | |
| parent | target: Don't set WBUS16 or SYNC bits in INQUIRY response (diff) | |
| download | linux-015487b89f27d91d95a056cdc3c85e6c729bff12.tar.xz linux-015487b89f27d91d95a056cdc3c85e6c729bff12.zip | |
target: Untangle front-end and back-end meanings of max_sectors attribute
se_dev_attrib.max_sectors currently has two independent meanings:
- It is reported in the block limits VPD page as the maximum transfer
length, ie the largest IO that the front-end (fabric) can handle.
Also the target core doesn't enforce this maximum transfer length.
- It is used to hold the size of the largest IO that the back-end can
handle, so we know when to split SCSI commands into multiple tasks.
Fix this by adding a new se_dev_attrib.fabric_max_sectors to hold the
maximum transfer length, and checking incoming IOs against that limit.
Signed-off-by: Roland Dreier <roland@purestorage.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'drivers/target/loopback')
0 files changed, 0 insertions, 0 deletions