From owner-freebsd-hackers Tue Jan 1 14:38:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m09.mx.aol.com (imo-m09.mx.aol.com [64.12.136.164]) by hub.freebsd.org (Postfix) with ESMTP id 83A2F37B405 for ; Tue, 1 Jan 2002 14:38:31 -0800 (PST) Received: from TD790@aol.com by imo-m09.mx.aol.com (mail_out_v31_r1.9.) id n.cc.449c7ad (4238); Tue, 1 Jan 2002 17:38:21 -0500 (EST) From: TD790@aol.com Message-ID: Date: Tue, 1 Jan 2002 17:38:21 EST Subject: Re: Running out of bufferspace To: drwilco@drwilco.net Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 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 In a message dated 01/01/2002 4:20:06 PM Eastern Standard Time, drwilco@drwilco.net writes: > >Just note that "no buffers" often means that the queue is full, not that > you > >are out of system buffers. You may be chasing a ghost. > > Well a queue should be cleaned shouldn't it? The mount_smbfs fails even > hours after I run the stresstest on my device. > > And which queue exactly are we talking about, and where/how do I check its > status? > 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 db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message