From owner-freebsd-hackers Wed Jan 2 8:43:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from artemis.drwilco.net (artemis.drwilco.net [209.167.6.62]) by hub.freebsd.org (Postfix) with ESMTP id 02BD737B41B for ; Wed, 2 Jan 2002 08:43:12 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g02Gh8R85844 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Wed, 2 Jan 2002 11:43:10 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020102174314.01e9f9b0@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 02 Jan 2002 17:51:57 +0100 To: hackers@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: Running out of bufferspace Cc: TD790@aol.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I think that fact that you still see the problem "hours later" indicates that >some internal device doesnt have a process to "revisit" the queue once you've >filled it. You can do the same thing fairly easily with a trafic generator >that uses raw sockets....check the ifp->if_snd.ifq_len for the device you are >sending on Well turns out my problem was two-fold. I'm indeed running out of ifp->if_snd on my xl0 interface, but I was also running out of space on my vmnet1 interface, but since I don't always run vmware it wasn't being emptied. Guess mount_smbfs needs a little patch.. I'll work on that =) Doc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message