From owner-freebsd-current@FreeBSD.ORG Thu May 5 14:40:58 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 837D9106566B for ; Thu, 5 May 2011 14:40:58 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3F6E68FC14 for ; Thu, 5 May 2011 14:40:57 +0000 (UTC) Received: by iyj12 with SMTP id 12so2642637iyj.13 for ; Thu, 05 May 2011 07:40:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WeAdxPaO1kYO+lKW5/kxgYfVlgoH6i+R4h6ctpbTNPg=; b=xPk2weuo5qFp18yIw887oNofnEzVmcAA/qyA9MwdQdJIVwMmjDwt3j5scjETo6cIvC Zg+cnYiYmxSKhdF6N0Kcw/F1VCgtPVdVElKV9ArKVMhSKwle5YdWQzBCCWSaAuYznXyF TVmW79hiYxxUBw/bmCOPnzCbfxJ2UD6sikdzM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LiOcfebt9MM7/xc59BJ+mJ9zMcDvw2og9eAx5Fx9MR5YVsVTWJfHUwuvtJSryR6cR9 uB+x+NAMBrUj4ymYN2nnxt3O7XvG3N2rEf+nyM30x+LijUwrh+qVIoOlwWsXJNOqm1+i fKNncd/vGtoNbPez60tff6r2rkS8JcceXzrSw= MIME-Version: 1.0 Received: by 10.42.151.73 with SMTP id d9mr730021icw.2.1304606457669; Thu, 05 May 2011 07:40:57 -0700 (PDT) Received: by 10.42.167.5 with HTTP; Thu, 5 May 2011 07:40:57 -0700 (PDT) In-Reply-To: <20110504070015.GB2700@direwolf> References: <4D94A354.9080903@sentex.net> <4DC07013.9070707@gmx.net> <4DC078BD.9080908@gmx.net> <20110504070015.GB2700@direwolf> Date: Thu, 5 May 2011 10:40:57 -0400 Message-ID: From: Arnaud Lacombe To: Alastair Hogge Content-Type: text/plain; charset=ISO-8859-1 Cc: Olivier Smedts , FreeBSD current mailing list , Jack Vogel , Michael Schmiedgen , Mike Tancsa Subject: Re: problems with em(4) since update to driver 7.2.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2011 14:40:58 -0000 Hi, On Wed, May 4, 2011 at 3:00 AM, Alastair Hogge wrote: > [.] > I also tried 2x, & 4x 25600 for max mbuff clusters via kern.ipc.nmbclusters. > This didn't help. > For the record, I did the math yestarday, checked the code. By default, a machine with 6 82574L-backed em(4) interfaces, with only 3 used (ie. brought up), initializes and work just fine with as low as 3076 mbuf clusters (1024*3 + 2). It has been transferring about 28k pps or 20Mbps of traffic (ICMP ping flood) since for the last 10h. Here is the `netstat -m' output: # netstat -m 2879/916/3795 mbufs in use (current/cache/total) 2877/199/3076/3076 mbuf clusters in use (current/cache/total/max) 2877/199 mbuf+clusters out of packet secondary zone in use (current/cache) 0/2/2/1537 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/768 9k jumbo clusters in use (current/cache/total/max) 0/0/0/384 16k jumbo clusters in use (current/cache/total/max) 6473K/635K/7108K bytes allocated to network (current/cache/total) 0/540580029/268859859 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/5/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines and, yes, allocation denial has sky-rocketed, but beside that the driver is stable. In that case, the uninitialized issue did not happen when the system booted. The complete machine should be able to initialize properly with 6146 clusters. - Arnaud