From owner-freebsd-drivers@FreeBSD.ORG Thu Feb 23 20:43:50 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CD29106564A for ; Thu, 23 Feb 2012 20:43:50 +0000 (UTC) (envelope-from adarsh.joshi@qlogic.com) Received: from VA3EHSOBE008.bigfish.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by mx1.freebsd.org (Postfix) with ESMTP id 03B2C8FC12 for ; Thu, 23 Feb 2012 20:43:49 +0000 (UTC) Received: from mail44-va3-R.bigfish.com (10.7.14.237) by VA3EHSOBE008.bigfish.com (10.7.40.28) with Microsoft SMTP Server id 14.1.225.23; Thu, 23 Feb 2012 20:43:48 +0000 Received: from mail44-va3 (localhost [127.0.0.1]) by mail44-va3-R.bigfish.com (Postfix) with ESMTP id 8B88CC03EB for ; Thu, 23 Feb 2012 20:43:48 +0000 (UTC) X-SpamScore: 0 X-BigFish: VPS0(zz9371Ic85fhzz1202hzz8275bh8275dhz2ei2a8h668h839h) X-Forefront-Antispam-Report: CIP:198.70.193.64; KIP:(null); UIP:(null); IPV:NLI; H:avexcashub1.qlogic.com; RD:avexcashub2.qlogic.com; EFVD:NLI Received-SPF: neutral (mail44-va3: 198.70.193.64 is neither permitted nor denied by domain of qlogic.com) client-ip=198.70.193.64; envelope-from=adarsh.joshi@qlogic.com; helo=avexcashub1.qlogic.com ; 1.qlogic.com ; Received: from mail44-va3 (localhost.localdomain [127.0.0.1]) by mail44-va3 (MessageSwitch) id 1330029826216051_28321; Thu, 23 Feb 2012 20:43:46 +0000 (UTC) Received: from VA3EHSMHS012.bigfish.com (unknown [10.7.14.242]) by mail44-va3.bigfish.com (Postfix) with ESMTP id 2FC463800C2 for ; Thu, 23 Feb 2012 20:43:46 +0000 (UTC) Received: from avexcashub1.qlogic.com (198.70.193.64) by VA3EHSMHS012.bigfish.com (10.7.99.22) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 23 Feb 2012 20:43:45 +0000 Received: from avexmb1.qlogic.org ([fe80::9545:3a4f:c131:467d]) by avexcashub2.qlogic.org ([::1]) with mapi; Thu, 23 Feb 2012 12:43:44 -0800 From: Adarsh Joshi To: "freebsd-drivers@freebsd.org" Date: Thu, 23 Feb 2012 12:43:42 -0800 Thread-Topic: Question on SOCKBUF_DEBUG option Thread-Index: AczxsYRqs56SBP3YR6WGFMna6BirsQAufuDw Message-ID: <5E4F49720D0BAD499EE1F01232234BA87437EBA678@AVEXMB1.qlogic.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-OriginatorOrg: qlogic.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Question on SOCKBUF_DEBUG option X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 20:43:50 -0000 Hello again, I am trying to debug socket timeout issues during my stress tests. Can anyo= ne suggest any debug options or flags I can turn on to get more information= ? Thanks a lot Adarsh From: Adarsh Joshi Sent: Wednesday, February 22, 2012 2:32 PM To: freebsd-drivers@freebsd.org Subject: Question on SOCKBUF_DEBUG option Hi, I read that the SOCKBUF_DEBUG option performs runtime consistency checks on= socket buffers. I am interested to know more about it. Can someone explain how this works and what information I can expect from i= t? Thanks regards Adarsh ________________________________ This message and any attached documents contain information from QLogic Cor= poration or its wholly-owned subsidiaries that may be confidential. If you = are not the intended recipient, you may not read, copy, distribute, or use = this information. If you have received this transmission in error, please n= otify the sender immediately by reply e-mail and then delete this message.