From owner-freebsd-net Mon May 15 13: 8:11 2000 Delivered-To: freebsd-net@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id A9BB737B807 for ; Mon, 15 May 2000 13:08:01 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FUM00AWEAALD5@falla.videotron.net> for net@FreeBSD.ORG; Mon, 15 May 2000 16:01:33 -0400 (EDT) Date: Mon, 15 May 2000 16:02:56 -0400 (EDT) From: Bosko Milekic Subject: Re: MFC of mbuf wait and other patch In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: net@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 13 May 2000, Mike Silbersack wrote: > Ok, I created the situation again, this time using fstat/lsof to see if I > could get any more additional information. Unfortunately, I've come up > dry. I'm sorry, as this is probably already the second time I'm asking you to do this (I unfortunately lost the first copy), but can you send me the code that you're using to simulate the exhaustion? (no need to CC is to the list, send directly to me). With that, I'll be able to get data and values that I can also try analyzing (now that this semester is officially over). > > What's occuring is that when I hit very close to all mbuf clusters and > mbufs full, apache answers the request, but is unable to stuff the full > ~15 of data (loopback's MTU size) into the send queue. It seems to wait > in mclalc for a few seconds, and goes back to the accept state. At this > point, the socket in question is no longer attached to any process, and > sits in the LAST_ACK state. However, unlike the pre-exhaustion sockets, > which are also in LAST_ACK, it seemingly never times out. I'll get back to you on this once I've tested it myself. On another note, how long have you waited for that "timeout?" > > I've been attempting to add to netstat so that it tells me more of the > socket internals so that I can hopefully see what's different about these > sockets than others, but it looks like adding all the various fields could > take some time; is there a tool which already shows this info > somewhere? Unfortunately, I'll be very busy during the next week, so I > won't get time to look much more into it. What you'd need in this case is also to get some information from the tcpcb in question. -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com bmilekic@dsuper.net * bmilekic@technokratis.com * b.milekic@marianopolis.edu "Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat and drink beer all day." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message