topic the Linux admin is trying to confirm if we can change the SVM "Target Max Recv Data Length" to match in Network and Storage Protocols

the Linux admin is trying to confirm if we can change the SVM "Target Max Recv Data Length" to match

Knowledgexchange — Wed, 04 Jun 2025 10:03:23 GMT

would like to know if there are any use cases to match the initiator & target mrdsl for OLAP (sequential) workload.

Can you verified with your team, if that parameter would affect the performance of OLAP (seq) vs OLTP (random) workload.

As the Linux admin is adamant that performance would suffer unless that “target-mrdsl” parameter on the target (NetApp) matches the initiator (Linux) “initiator-mrdsl” for the OLAP (sequential) workload.

Re: the Linux admin is trying to confirm if we can change the SVM "Target Max Recv Data Length&

hmoubara — Wed, 16 Mar 2022 06:08:29 GMT

Hello,

The initiator or target declares the maximum data segment length in bytes it can receive in an iSCSI PDU.
so per example, if an initiator advertised MRDSL=16MB, that would mean that the initiator is willing to accept PDUs with
a data segment UP TO 16MB. ONTAP never sends a PDU larger than 64KB, but since 64KB < 16MB, this would not be a compliance or interop issue.

Hope this answer your question.

Thanks

Re: the Linux admin is trying to confirm if we can change the SVM "Target Max Recv Data Length&

Knowledgexchange — Fri, 18 Mar 2022 02:33:42 GMT

Re: “ONTAP never sends a PDU larger than 64KB, but since 64KB < 16MB, this would not be a compliance or interop issue.”

So ONTAP would not send out (target-mrdsl) larger than 64KB regardless of the workload (random or sequential)?