LL2 today is interrupt driven - when tx/rx completion arrives [or any other indication], qed needs to operate on the connection and pass the information to the protocol-driver [or internal qed consumer]. Since we have several flavors of ll2 employeed by the driver, each handler needs to do an if-else to determine the right functionality to use based on the connection type. In order to make things more scalable [given that we're going to add additional types of ll2 flavors] move the infrastrucutre into using a callback-based approach - the callbacks would be provided as part of the connection's initialization parameters. Signed-off-by: Michal Kalderon <Michal.Kalderon@cavium.com> Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
|---|---|---|
| .. | ||
| common_hsi.h | ||
| eth_common.h | ||
| fcoe_common.h | ||
| iscsi_common.h | ||
| qed_chain.h | ||
| qed_eth_if.h | ||
| qed_fcoe_if.h | ||
| qed_if.h | ||
| qed_iov_if.h | ||
| qed_iscsi_if.h | ||
| qed_ll2_if.h | ||
| qed_roce_if.h | ||
| qede_roce.h | ||
| rdma_common.h | ||
| roce_common.h | ||
| storage_common.h | ||
| tcp_common.h | ||