From owner-freebsd-atm@FreeBSD.ORG  Mon Oct  6 03:09:22 2003
Return-Path: <owner-freebsd-atm@FreeBSD.ORG>
Delivered-To: freebsd-atm@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A941D16A4B3
	for <freebsd-atm@freebsd.org>; Mon,  6 Oct 2003 03:09:22 -0700 (PDT)
Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de
	[193.174.154.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 19FE043FDD
	for <freebsd-atm@freebsd.org>; Mon,  6 Oct 2003 03:09:21 -0700 (PDT)
	(envelope-from brandt@fokus.fraunhofer.de)
Received: from beagle (beagle [193.175.132.100])h96A9Hh17591;
	Mon, 6 Oct 2003 12:09:17 +0200 (MEST)
Date: Mon, 6 Oct 2003 12:09:17 +0200 (CEST)
From: Harti Brandt <brandt@fokus.fraunhofer.de>
To: Vincent Jardin <vjardin@wanadoo.fr>
In-Reply-To: <200310030905.17383.vjardin@wanadoo.fr>
Message-ID: <20031006120414.F41960@beagle.fokus.fraunhofer.de>
References: <20031002222904.B6457230CA@arrakis.solutions.net.pl>
 <200310030905.17383.vjardin@wanadoo.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: bucari@prosum.fr
cc: freebsd-atm <freebsd-atm@freebsd.org>
Subject: Re: Re: patm, idt, ipfw - next adentures
X-BeenThere: freebsd-atm@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ATM for FreeBSD! <freebsd-atm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-atm>,
	<mailto:freebsd-atm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-atm>
List-Post: <mailto:freebsd-atm@freebsd.org>
List-Help: <mailto:freebsd-atm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-atm>,
	<mailto:freebsd-atm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2003 10:09:22 -0000

On Fri, 3 Oct 2003, Vincent Jardin wrote:

VJ>Hi,
VJ>
VJ>I do not see the following error message that you had yesterday ?
VJ>
VJ>Oct  2 03:18:45 ordos /kernel: proatm0: i=101, status=00080008
VJ>Oct  2 03:18:45 ordos /kernel: proatm0: not enough large buffers.
VJ>
VJ>Are you using exactly the same configuration ? Or how long do you have to wait
VJ>before getting the "not enough large buffers" error ?
VJ>
VJ>Regards,
VJ>  Vincent
VJ>
VJ>
VJ>> This is without ipfw (I removed ipfw from kernel).
VJ>
VJ>> proatm0: <PROSUM PROATM adapter> port 0xd400-0xd4ff mem
VJ>> 0xfb000000-0xfb3fffff,0xf8800000-0xf8800fff
VJ>> proatm0: ATM card is PROATM-155 or IDT, PHY=PM5346 or IDT77155
VJ>> proatm0: 128K words of RAM up to 4096 PVC
VJ>> proatm0: MAC address 00:c0:fd:00:7b:a0, HWrev=6
VJ>[...]
VJ>> proatm0: proatm_openvcc: 0/141, PCR=15000, SCR=15000
VJ>> proatm0: txopen UBR connection for 0/142
VJ>> proatm0: proatm_openvcc: 0/142, PCR=15000, SCR=15000
VJ>> proatm0: txopen UBR connection for 0/143
VJ>[...]
VJ>> proatm0 BUFFER STATUS: small=277/510, large=304/510.
VJ>> proatm0 BUFFER STATUS: small=256/510, large=283/510.

This suggests that you have increased bufsmall and buflarge to 510,
correct? In this case I think the resupply algorithm will leak mbufs. I
think the leak shouldn't happen when you set both variables not larger
than 278.

 VJ>
VJ>Oct  2 03:18:45 ordos /kernel: proatm0: i=101, status=00080008
VJ>Oct  2 03:18:45 ordos /kernel: proatm0: not enough large buffers.

As I said in another mail, this may happen if you're assembling PDUs on a
lot of VCs simultaneously (when the number of VCs approaches the limit on
free buffers (or half that number?)).

harti
-- 
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
brandt@fokus.fraunhofer.de, harti@freebsd.org