From owner-freebsd-hackers Tue Dec 22 16:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23954 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 16:19:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23949 for ; Tue, 22 Dec 1998 16:19:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA08154; Tue, 22 Dec 1998 16:19:43 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 16:19:43 -0800 (PST) From: Matthew Dillon Message-Id: <199812230019.QAA08154@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: M_KERNEL in sys/malloc.h ??? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know what M_KERNEL is sys/malloc.h is supposed to do? It is used in precisely two places in the code as far as I can tell: vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { vm/swap_pager.c: spc->spc_bp = malloc(sizeof(*bp), M_TEMP, M_KERNEL); But kern/kern_malloc.c doesn't appear to really use it. On the otherhand I do see lots of absolute comparison of the malloc 'flags' to M_WAITOK (0) or M_NOWAIT which the use of M_KERNEL would interfere with. I can't tell if the side effects are something that are expected, or if the side effects are a bug. Anybody know? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message