kernel/git/stable/linux.git/drivers/net/cxgb3/version.h, branch master

chelsio: Move the Chelsio drivers

2011-08-11T02:54:52+00:00

Moves the drivers for the Chelsio chipsets into drivers/net/ethernet/chelsio/ and the necessary Kconfig and Makefile changes. CC: Divy Le Ray CC: Dimitris Michailidis CC: Casey Leedom Signed-off-by: Jeff Kirsher

cxgb3: request 7.10 firmware

2010-06-26T04:33:13+00:00

The driver requests FW 7.10 Bump up driver version. Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: Update FW to 7.4.0

2009-06-04T04:01:50+00:00

Update FW to 7.4. Bump up driver revision. Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: update driver version

2009-03-13T18:30:49+00:00

update driver version to 1.1.1-ko Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: update FW

2009-03-13T18:30:48+00:00

Update FW to 7.1 Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: Add multiple Tx queue support.

2008-12-16T09:09:39+00:00

Implement NIC Tx multiqueue. Bump up driver version. Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: extend copyrights to 2008

2008-10-14T01:47:30+00:00

Update copyright banner to 2008. Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

cxgb3: update driver version

2008-10-14T01:47:02+00:00

Add a field to the driver versioning info. Update version to 1.1.0. Signed-off-by: Divy Le Ray Signed-off-by: David S. Miller

RDMA/cxgb3: Fixes for zero STag

2008-07-15T06:48:53+00:00

Handling the zero STag in receive work request requires some extra logic in the driver: - Only set the QP_PRIV bit for kernel mode QPs. - Add a zero STag build function for recv wrs. The uP needs a PBL allocated and passed down in the recv WR so it can construct a HW PBL for the zero STag S/G entries. Note: we need to place a few restrictions on zero STag usage because of this: 1) all SGEs in a recv WR must either be zero STag or not. No mixing. 2) an individual SGE length cannot exceed 128MB for a zero-stag SGE. This should be OK since it's not really practical to allocate such a large chunk of pinned contiguous DMA mapped memory. - Add an optimized non-zero-STag recv wr format for kernel users. This is needed to optimize both zero and non-zero STag cracking in the recv path for kernel users. - Remove the iwch_ prefix from the static build functions. - Bump required FW version. Signed-off-by: Steve Wise

RDMA/cxgb3: Support peer-2-peer connection setup

2008-04-29T20:46:52+00:00

Open MPI, Intel MPI and other applications don't respect the iWARP requirement that the client (active) side of the connection send the first RDMA message. This class of application connection setup is called peer-to-peer. Typically once the connection is setup, _both_ sides want to send data. This patch enables supporting peer-to-peer over the chelsio RNIC by enforcing this iWARP requirement in the driver itself as part of RDMA connection setup. Connection setup is extended, when the peer2peer module option is 1, such that the MPA initiator will send a 0B Read (the RTR) just after connection setup. The MPA responder will suspend SQ processing until the RTR message is received and reply-to. In the longer term, this will be handled in a standardized way by enhancing the MPA negotiation so peers can indicate whether they want/need the RTR and what type of RTR (0B read, 0B write, or 0B send) should be sent. This will be done by standardizing a few bits of the private data in order to negotiate all this. However this patch enables peer-to-peer applications now and allows most of the required firmware and driver changes to be done and tested now. Design: - Add a module option, peer2peer, to enable this mode. - New firmware support for peer-to-peer mode: - a new bit in the rdma_init WR to tell it to do peer-2-peer and what form of RTR message to send or expect. - process _all_ preposted recvs before moving the connection into rdma mode. - passive side: defer completing the rdma_init WR until all pre-posted recvs are processed. Suspend SQ processing until the RTR is received. - active side: expect and process the 0B read WR on offload TX queue. Defer completing the rdma_init WR until all pre-posted recvs are processed. Suspend SQ processing until the 0B read WR is processed from the offload TX queue. - If peer2peer is set, driver posts 0B read request on offload TX queue just after posting the rdma_init WR to the offload TX queue. - Add CQ poll logic to ignore unsolicitied read responses. Signed-off-by: Steve Wise Signed-off-by: Roland Dreier