From owner-freebsd-net@FreeBSD.ORG Wed Mar 30 17:06:57 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 EEEC11065672; Wed, 30 Mar 2011 17:06:57 +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 98FB38FC16; Wed, 30 Mar 2011 17:06:57 +0000 (UTC) Received: by iwn33 with SMTP id 33so1810252iwn.13 for ; Wed, 30 Mar 2011 10:06: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 :content-transfer-encoding; bh=VQ/D77275z+OmPcS/oezEH2bQNo+mKvWeUluwYK0sDA=; b=HyfPSY1JQ2eKIBvecrmAulN1W/CSlhFkTmwZhyHc5FQOWvR9R3JBoNHtRvekcPePlD 29RhWOLfoZwGxm5Vj7NbzmvK3vz2mwT63KuXqUT+1VqVUBXExHgrz5rPUbr+y7s5CSUI qhw1/5h+p4tMOgmsY6Jw4Jom03eRIoYdCRk90= 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=gMA8Se5RxiRri7/arZSDqqMReJDKkJLXb3hQHUSuO1WxVZjk2pEmDKHWg6mklAoi3a cFH1whA/JXiOKYaU2rzkZj2379/7V0eYuN/+jKEOMuIi1zJFnKCShU6sB8uPJXtrPLE4 jgx5qpBcVRVGDl3pzE4PJn6xRX5ySW8ts5pi4= MIME-Version: 1.0 Received: by 10.43.60.71 with SMTP id wr7mr1367279icb.148.1301504817002; Wed, 30 Mar 2011 10:06:57 -0700 (PDT) Received: by 10.42.146.72 with HTTP; Wed, 30 Mar 2011 10:06:56 -0700 (PDT) In-Reply-To: <4D935DF6.90906@FreeBSD.org> References: <4D923931.2070606@zonov.org> <4D92BB71.5000900@FreeBSD.org> <4D935DF6.90906@FreeBSD.org> Date: Wed, 30 Mar 2011 13:06:56 -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 17:06:58 -0000 Hi, On Wed, Mar 30, 2011 at 12:44 PM, Doug Barton wrote: > On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: >> >> Hi, >> >> On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton =A0wrote= : > >> 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 >>> some >>> 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. > > If you're facing that situation then obviously your system is constrained= by > hardware. No. We are taking about exceptional recoverable situation not handled by the software, it should not bring the complete system down. If you're swapping code has defect, you do not tell one to buy more RAM not to trigger the defective code, you fix the code. The situation is similar here. - Arnaud