Re: AW: ACK behaviour difference LRO/GRO

2013-10-29 Thread Or Gerlitz 

On 29/10/2013 13:10, Markus Stockhausen wrote:

Just to be on the right way: What are the basics to get GRO working
with a ConnectX (not 2 or 3) card in 2044 MTU datagram mode?

- enable GRO with ethtool.
- Activate Coalescing with ethtool? If yes how?
GRO is SW element of the network stack, so the HCA doesn't matter, you 
need IPoIB to support that correct and enable it with ethtool

--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: AW: ACK behaviour difference LRO/GRO

2013-10-29 Thread Erez Shitrit 

בתאריך 10/29/2013 1:43 PM, ציטוט Or Gerlitz:

On 29/10/2013 13:10, Markus Stockhausen wrote:

Just to be on the right way: What are the basics to get GRO working
with a ConnectX (not 2 or 3) card in 2044 MTU datagram mode?

- enable GRO with ethtool.
- Activate Coalescing with ethtool? If yes how?
GRO is SW element of the network stack, so the HCA doesn't matter, you 
need IPoIB to support that correct and enable it with ethtool

--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html


In addition to what Or just wrote,
GRO currently doesn't work on ipoib interfaces, that according to bad 
handling mac address that are not 6 bytes (we have plans to fix that in 
the near future), that is the reason you don't see 64k packets on 
tcpdump (like you see in LRO).


you have few options:
1. use old kernels and enable LRO (which works fine with ipoib)
2. use CM mode instead of UD, that probably will improve the performance.

Thanks, Erez
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: AW: ACK behaviour difference LRO/GRO

2013-10-29 Thread Or Gerlitz 

On 29/10/2013 14:55, Erez Shitrit wrote:

In addition to what Or just wrote,
GRO currently doesn't work on ipoib interfaces, that according to bad 
handling mac address that are not 6 bytes (we have plans to fix that 
in the near future), that is the reason you don't see 64k packets on 
tcpdump (like you see in LRO). 


I just checked with net-next which is 3.12-rc6+ and there IS 
aggregationfor datagram mode


15:56:40.983883 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801688305:1801692289, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 3984
15:56:40.983942 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801692289:1801756033, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 63744
15:56:40.984027 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801756033:1801819777, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 63744
15:56:40.984079 IP 192.168.20.17.40861  192.168.20.18.55714: Flags 
[.], ack 1801688305, win 1544, options [nop,nop,TS val 305403520 ecr 
44014459], length 0
15:56:40.984104 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801819777:1801823649, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 3872
15:56:40.984159 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801823649:1801883521, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 59872
15:56:40.984214 IP 192.168.20.17.40861  192.168.20.18.55714: Flags 
[.], ack 1801819777, win 1009, options [nop,nop,TS val 305403520 ecr 
44014459], length 0
15:56:40.984241 IP 192.168.20.18.55714  192.168.20.17.40861: Flags 
[.], seq 1801883521:1801887393, ack 1, win 220, options [nop,nop,TS 
val 44014459 ecr 305403520], length 3872



--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html