From owner-freebsd-hackers Thu Jul 29 10: 0:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id EE2C715101 for ; Thu, 29 Jul 1999 10:00:09 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA74615; Thu, 29 Jul 1999 09:59:25 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 09:59:25 -0700 (PDT) From: Matthew Dillon Message-Id: <199907291659.JAA74615@apollo.backplane.com> To: Jason Thorpe Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: MADV_SEQUENTIAL and GNU Grep References: <199907291655.JAA29585@lestat.nas.nasa.gov> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, 30 Jul 1999 01:50:28 +0900 : "Daniel C. Sobral" wrote: : : > Could you please elaborate on "permanent"? To what structure the : > information is currently attached, and what, if anything, can make : > that structure "go away", short of a reboot? : :As permanent as the object ... i.e. as long as the object persists. : : > Of course, we could MADV_NORMAL afterwards, though that would : > require changing more than one character. I'm not sure I'm ready for : > so much coding... :-) : :No, it's not appropriate to work around a kernel bug in this fashion. : : -- Jason R. Thorpe I'm willing to fix it. If NetBSD has moved it to the map entry then I can move it here without core screaming at me too much, though every time I do any work I have to balance the fun against the frustration of not being able to commit it myself. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message