Thread (8 messages) flat view 8 messages, 2 authors, 2016-05-10
DORMANTno replies

Revision v1 of 3 in this series.

Revisions (3)
  1. v1 [diff vs current]
  2. v1 current
  3. v2 [diff vs current]

Re: [PATCH 5/6] drivers: net: xgene: Using static MSS values

From: David Miller <davem@davemloft.net>
Date: 2016-05-10 19:53:54
Also in: linux-arm-kernel

From: Iyappan Subramanian <redacted>
Date: Mon,  9 May 2016 17:04:15 -0700
Due to the nature of hardware design for TSO, if the MSS values that are
stored in the register, changes during TSO operation, data corruption may
occur.

This patch fixes the issue by using one of the predefined MSS values.

Signed-off-by: Iyappan Subramanian <redacted>
Tested-by: Toan Le <redacted>
This is a very serious quality of implementation issue.

And it could quietly kill performance for some users, and there is no
way for them to find out that this is happening.

If you use a predefined set of MSS values, if the MSS value we need is
between two of them then there is going to be wasted space on the
wire.  It's can therefore certainly be better to not do TSO in that
case.

I think you absolutely need to disable TSO by default, and require the
user to explicitly turn it on, unless you can fix this problem in
another way.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help