Searched refs:iwarp (Results 1 – 8 of 8) sorted by relevance
310 } iwarp; member
219 struct ecore_iwarp_info iwarp; member
304 struct ecore_iwarp_params iwarp; member
1133 10. Request: Add ecore support to recognize the iwarp app TLV, and configure
621 struct iwarp_init_func_params iwarp; member786 struct iwarp_offload_params iwarp /* iWARP connection offload params */; member
1218 For iwarp support, modification to existing structures and functions names will be made to ease dis…1222 \item ecore\_iwarp\_xxx will be used for iwarp specific structures, fields and functions1250 \texttt{iwarp\_port} & TCP port number to be used for the iwarp traffic\\ \hline1268 \texttt{iwarp\_flags} & TCP related flags that can be controlled by user. 1273 \texttt{iwarp\_crc\_needed} & Control whether CRC should be used. \\ \hline1274 …\texttt{iwarp\_rcv\_wnd\_size} & ecore will calculate the receive window scale from this. This num…1345 \subsubsection{iwarp\_create\_listen}1412 \caption{iwarp state machine form hilland verbs}1417 The interface into ecore is done with the states of RoCE and translated internally to iwarp states.…1488 …iwarp offloaded connections. If an app tlv which matches this port is indicated by MFW, all offloa…
419 bool iwarp; member
3951 p->iwarp = TRUE; in i40e_parse_discover_capabilities()3953 "HW Capability: iWARP = %d\n", p->iwarp); in i40e_parse_discover_capabilities()7503 hw->dev_caps.iwarp = (msg->vf_cap_flags & in i40e_vf_parse_hw_config()