From owner-cvs-all Sat Nov 24 20:43: 2 2001 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 838EE37B405; Sat, 24 Nov 2001 20:42:59 -0800 (PST) Received: (from bmilekic@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id fAP4gsv29290; Sat, 24 Nov 2001 20:42:54 -0800 (PST) (envelope-from bmilekic) Message-Id: <200111250442.fAP4gsv29290@freefall.freebsd.org> From: Bosko Milekic Date: Sat, 24 Nov 2001 20:42:54 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/kern subr_mbuf.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bmilekic 2001/11/24 20:42:54 PST Modified files: sys/kern subr_mbuf.c Log: Context: For an object type, we maintain a variable mb_mapfull. It is 0 by default and is only raised to 1 in one place: when an mb_pop_cont() fails for the first time, on the assumption that the reason for the failure is due to the underlying map for the object (e.g. clust_map, mbuf_map) being exhausted. Problem and Changes: Change how we define "mb_mapfull." It now means: "set to 1 when the first mb_pop_cont() fails only in the kmem_malloc()-ing of the object, and only if the call was with the M_TRYWAIT flag." This is a more conservative definition and should avoid odd [but theoretically possible] situations from occuring. i.e. we had set mb_mapfull to 1 thinking the map for the object was actually exhausted when we _actually_ failed in malloc()ing the space for the bucket structure managing the objects in the page we're allocating. Revision Changes Path 1.10 +3 -2 src/sys/kern/subr_mbuf.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message