From owner-freebsd-hackers Thu Jul 29 11:56: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 3855215185 for ; Thu, 29 Jul 1999 11:55:43 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id JAA29585; Thu, 29 Jul 1999 09:55:40 -0700 (PDT) Message-Id: <199907291655.JAA29585@lestat.nas.nasa.gov> To: "Daniel C. Sobral" Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: MADV_SEQUENTIAL and GNU Grep Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 29 Jul 1999 09:55:39 -0700 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message