From owner-p4-projects@FreeBSD.ORG  Fri Jan 11 17:47:33 2008
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 4847B16A479; Fri, 11 Jan 2008 17:47:33 +0000 (UTC)
Delivered-To: perforce@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0BD3716A46B
	for <perforce@FreeBSD.org>; Fri, 11 Jan 2008 17:47:33 +0000 (UTC)
	(envelope-from swise@FreeBSD.org)
Received: from repoman.freebsd.org (repoman.freebsd.org
	[IPv6:2001:4f8:fff6::29])
	by mx1.freebsd.org (Postfix) with ESMTP id E799F13C47E
	for <perforce@FreeBSD.org>; Fri, 11 Jan 2008 17:47:32 +0000 (UTC)
	(envelope-from swise@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.14.1/8.14.1) with ESMTP id m0BHlWQW019257
	for <perforce@FreeBSD.org>; Fri, 11 Jan 2008 17:47:32 GMT
	(envelope-from swise@FreeBSD.org)
Received: (from perforce@localhost)
	by repoman.freebsd.org (8.14.1/8.14.1/Submit) id m0BHlWbl019254
	for perforce@freebsd.org; Fri, 11 Jan 2008 17:47:32 GMT
	(envelope-from swise@FreeBSD.org)
Date: Fri, 11 Jan 2008 17:47:32 GMT
Message-Id: <200801111747.m0BHlWbl019254@repoman.freebsd.org>
X-Authentication-Warning: repoman.freebsd.org: perforce set sender to
	swise@FreeBSD.org using -f
From: Steve Wise <swise@FreeBSD.org>
To: Perforce Change Reviews <perforce@FreeBSD.org>
Cc: 
Subject: PERFORCE change 133058 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2008 17:47:33 -0000

http://perforce.freebsd.org/chv.cgi?CH=133058

Change 133058 by swise@swise:vic10:iwarp on 2008/01/11 17:47:09

	
	Set the max_qp_init_rd_atom attribute in query_device
	
	The device attribute max_qp_init_rd_atom is not getting set
	in cxgb3's query_device method.  Version 1.0.4 of librdmacm
	now validates the user's requested initiator and responder
	resources against the max supported by the device.  Since
	iw_cxgb3 wasn't setting this attribute (and it defaulted
	to 0), all rdma_connect()s fail if there are initiator
	resources requested by the app.  Fix this by setting the
	correct value in iwch_query_device().

Affected files ...

.. //depot/projects/iwarp/sys/dev/cxgb/ulp/iw_cxgb/iw_cxgb_iwch_provider.c#5 edit

Differences ...

==== //depot/projects/iwarp/sys/dev/cxgb/ulp/iw_cxgb/iw_cxgb_iwch_provider.c#5 (text+ko) ====

@@ -1053,6 +1053,7 @@
 	props->max_sge = dev->attr.max_sge_per_wr;
 	props->max_sge_rd = 1;
 	props->max_qp_rd_atom = dev->attr.max_rdma_reads_per_qp;
+	props->max_qp_init_rd_atom = dev->attr.max_rdma_reads_per_qp;
 	props->max_cq = dev->attr.max_cqs;
 	props->max_cqe = dev->attr.max_cqes_per_cq;
 	props->max_mr = dev->attr.max_mem_regs;