From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Max Transfer Length
Date: Tue, 02 May 2017 18:17:31 +0000 [thread overview]
Message-ID: <92B481CB-221A-484D-B6E1-408FC922292C@intel.com> (raw)
In-Reply-To: 84912AF4-2BEE-4803-8C8B-5D885F551D92@cloudsimple.com
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
> On May 2, 2017, at 1:52 AM, Kumaraparameshwaran Rathnavel <krath(a)cloudsimple.com> wrote:
>
> Hi All,
>
> Is it possible to change the Transfer size of the iSCSI initiator and target to a configurable value. Right now MAXRECVDATASEGMENTLENGTH is 65536. If I change this to 4096, I still see the initiator requesting more than 4k. Is there any other parameters that i should change at the target level to get read and write requests exactly of the Block size and the Block size that I use is 4096.
Hi Param,
MaxRecvSegmentLength only limits the maximum size of iSCSI PDUs - it does not limit the size of SCSI I/O commands. So limiting MaxRecvSegmentLength to 4KB just means that the data for a 1MB SCSI I/O will basically have to be sent as a sequence of 256 4KB Data PDUs.
Note also that this value is negotiated twice - once for the maximum length that the target can send to the initiator, and another for the maximum length then initiator can send to the target.
If you want to artificially limit the maximum size of I/O sent by a Linux iSCSI initiator for testing purposes, you can modify /sys/block/sdX/queue/max_sectors_kb.
-Jim
next reply other threads:[~2017-05-02 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 18:17 Harris, James R [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-03 2:48 [SPDK] Max Transfer Length Kumaraparameshwaran Rathnavel
2017-05-02 8:52 Kumaraparameshwaran Rathnavel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92B481CB-221A-484D-B6E1-408FC922292C@intel.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.