From owner-freebsd-stable Wed Sep 8 0: 7:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 71E8F14FF9 for ; Wed, 8 Sep 1999 00:07:36 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (robinson@TCE-E-7-178-180.bta.net.cn [202.106.178.180]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id PAA20565 for ; Wed, 8 Sep 1999 15:01:21 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id PAA00509 for freebsd-stable@freebsd.org; Wed, 8 Sep 1999 15:03:31 +0800 (CST) (envelope-from robinson) Date: Wed, 8 Sep 1999 15:03:31 +0800 (CST) From: Michael Robinson Message-Id: <199909080703.PAA00509@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Vinum, malloc, and swap Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the Vinum intro: "In order to perform its functionality, Vinum allocates a large number of dynamic data structures. Currently these structures are allocated by calling kernel malloc. This is a potential problem, since malloc interacts with the virtual memory system and may trigger a page fault. The potential for a deadlock exists if the page fault requires a transfer to a Vinum volume. It is probable that Vinum will modify its allocation strategy by reserving a small number of buffers when it starts and using these if a malloc request fails." Has this "potential problem" been addressed in the Vinum in Stable? If not, is there any other way to prevent a system panic if a drive containing a swap partition fails? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message