From owner-freebsd-stable@FreeBSD.ORG Wed Feb 22 20:18:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A864106564A; Wed, 22 Feb 2012 20:18:20 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 87C058FC0A; Wed, 22 Feb 2012 20:18:19 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so458680wib.13 for ; Wed, 22 Feb 2012 12:18:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=MNKO8AUKN4XcZzcNgK+huXunvuMsSkOTvgaGzaEb7Pg=; b=E8r5UUGByl9FdIZS8qlSs5C7EVoxJG8LU+vPDytvSxmxvjSk3rfpT6LDyBwm4z7U91 q7XLjpecnMOJ3k6BPxC0HUhxpTHSYhYRiJ5+LAERDLGO1gYV28xQJjnmosxeWeRQ0ogr iamDg00OUe3sOAb3qt8NEX2IbZbNj5fqhzsgo= MIME-Version: 1.0 Received: by 10.180.93.232 with SMTP id cx8mr32890006wib.14.1329940590025; Wed, 22 Feb 2012 11:56:30 -0800 (PST) Received: by 10.180.102.97 with HTTP; Wed, 22 Feb 2012 11:56:29 -0800 (PST) Date: Wed, 22 Feb 2012 11:56:29 -0800 Message-ID: From: Jack Vogel To: FreeBSD Net , FreeBSD stable , re Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: nmbclusters: how do we want to fix this for 8.3 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 20:18:20 -0000 Using igb and/or ixgbe on a reasonably powered server requires 1K mbuf clusters per MSIX vector, that's how many are in a ring. Either driver will configure 8 queues on a system with that many or more cores, so 8K clusters per port... My test engineer has a system with 2 igb ports, and 2 10G ixgbe, this is hardly heavy duty, and yet this exceeds the default mbuf pool on the installed kernel (1024 + maxusers * 64). Now, this can be immediately fixed by a sysadmin after that first boot, but it does result in the second driver that gets started to complain about inadequate buffers. I think the default calculation is dated and should be changed, but am not sure the best way, so are there suggestions/opinions about this, and might we get it fixed before 8.3 is baked? Cheers, Jack