From owner-freebsd-net@FreeBSD.ORG Thu Oct 25 17:30:40 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE11D4C5 for ; Thu, 25 Oct 2012 17:30:40 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6498FC14 for ; Thu, 25 Oct 2012 17:30:40 +0000 (UTC) Received: from [10.9.208.27] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Thu, 25 Oct 2012 10:26:35 -0700 X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261 Received: from IRVEXCHSMTP1.corp.ad.broadcom.com (10.9.207.51) by irvexchmb05.corp.ad.broadcom.com (10.9.208.27) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 25 Oct 2012 10:27:42 -0700 Received: from IRVEXCHMB11.corp.ad.broadcom.com ( [fe80::9cdd:3a57:8694:f610]) by Irvexchsmtp1.corp.ad.broadcom.com ( [fe80::f003:4754:d9bd:c345%12]) with mapi id 14.01.0355.002; Thu, 25 Oct 2012 10:27:42 -0700 From: "David Christensen" To: "Eugene Mitrofanov" , "freebsd-net@freebsd.org" Subject: RE: dev.bce.3.mbuf_alloc_failed_count increases permanently Thread-Topic: dev.bce.3.mbuf_alloc_failed_count increases permanently Thread-Index: AQHNqIcx9qHWzixm9UeSl2IG5LrxgpfKWXzw Date: Thu, 25 Oct 2012 17:27:41 +0000 Message-ID: <3A5015FE9E557D448AF7238AF0ACE20A24B0F4@IRVEXCHMB11.corp.ad.broadcom.com> References: <201210121812.37557.eugene@imedia.ru> In-Reply-To: <201210121812.37557.eugene@imedia.ru> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.208.64] MIME-Version: 1.0 X-WSS-ID: 7C97A9C141411624745-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 17:30:40 -0000 > sysctl -a | g bce.3|g -vE '(%|stat)'; echo; sleep 10; sysctl -a | g bce.= 3| > g -vE '(%|stat)'; echo; netstat -m >=20 > dev.bce.3.l2fhdr_error_count: 0 > dev.bce.3.mbuf_alloc_failed_count: 2098854 > dev.bce.3.mbuf_frag_count: 2655285 > dev.bce.3.dma_map_addr_rx_failed_count: 0 > dev.bce.3.dma_map_addr_tx_failed_count: 57 > dev.bce.3.unexpected_attention_count: 0 > dev.bce.3.com_no_buffers: 0 >=20 > dev.bce.3.l2fhdr_error_count: 0 > dev.bce.3.mbuf_alloc_failed_count: 2098856 > dev.bce.3.mbuf_frag_count: 2655288 > dev.bce.3.dma_map_addr_rx_failed_count: 0 > dev.bce.3.dma_map_addr_tx_failed_count: 57 > dev.bce.3.unexpected_attention_count: 0 > dev.bce.3.com_no_buffers: 0 >=20 >=20 > Any suggestions? What is the reason of this? It's normal in a system under load, the kernel can't always allocate memory when requested by the driver. The result is that RX frames will be dropped as the driver reuses an existing mbuf, a response taken by many other drivers. If you notice rapid increases during certain system operations then you should consider increasing the amount of system memory. Dave