From owner-freebsd-net@FreeBSD.ORG Wed Mar 30 14:20:50 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C584D106566B for ; Wed, 30 Mar 2011 14:20:50 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8C18C8FC12 for ; Wed, 30 Mar 2011 14:20:50 +0000 (UTC) Received: by iwn33 with SMTP id 33so1634941iwn.13 for ; Wed, 30 Mar 2011 07:20:49 -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 :content-transfer-encoding; bh=fIxPhEtAEjiup/ZHMVK4wjxr2CjCtkTEYARmT980bQQ=; b=SdrJflvq18qV1irAAIjNSLE7g/qilu+pOHIZmf+RddpBKMXO3NUjwwTUipmoZ1Kars 8zHkS1wxxhW+V/4qeKMi5/NB/W2Dv7d/YgI1t/9dFr8SOB/u72UwIvhL4YvmgOiXzISo iM0mnqTZWt3ZqMBufkzeUW6TNX0Tjlg8IU/PI= 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:content-transfer-encoding; b=J34IRXxMNdqYYYQg/5Fbfb+neCjdJ7T9vGGtcxthV1oRZHT7iLRGQGZttWm3phYHoO 2k0iIUHyC/LWtrZ9j1Y8HF9GFpXIBAWRx/mlR8Dcm3qDtxeJArS1tqnRrbBLSMHz7pqp MlxXSRVZSYdTUR5ObMVZqE52ebnmjkf0L4ulw= MIME-Version: 1.0 Received: by 10.231.180.94 with SMTP id bt30mr1360548ibb.23.1301494748020; Wed, 30 Mar 2011 07:19:08 -0700 (PDT) Received: by 10.42.146.72 with HTTP; Wed, 30 Mar 2011 07:19:07 -0700 (PDT) In-Reply-To: <4D92BB71.5000900@FreeBSD.org> References: <4D923931.2070606@zonov.org> <4D92BB71.5000900@FreeBSD.org> Date: Wed, 30 Mar 2011 10:19:07 -0400 Message-ID: From: Arnaud Lacombe To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: igb(4) won't start with "igb0: Could not setup receive structures" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 14:20:50 -0000 Hi, On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton wrote: > On 03/29/2011 22:07, Arnaud Lacombe wrote: >> >> ... or maintain internal changes to the driver to make it not that memor= y >> hungry/behave well under memory pressure, especially on system where >> memory_is_ =A0a constraint. > > If you come up with patches, I'm sure everyone would like to see them. > No, I came with a patch, Jack sent it explicitly to /dev/null, telling me that what I was checking was not available in the mode the driver was in. Then I took the chip documentation, quoted all the chapters which lead me to believe that what I was checking _was_ available in the mode the driver was. I never got an answer. Unfortunately, all these discussion are not publicly available because Jack like doing things off the list. The only things I've been able to get from Jack is "We, at Intel, test em(4) at 256k nmbclusters. We do not have problem. If you have problem, raise nmbcluster.". 256k nmbcluster in my environment is not acceptable. > Meanwhile, there are times where memory IS a constraint, and there are so= me > things you can't do without more of it. > yes, but the driver should not need a manual reset between the time resource are (heavily) scarce and the time it became available again. - Arnaud