From owner-freebsd-hackers Thu Jul 29 11:55:52 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 63E5714BC9 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 KAA00408; Thu, 29 Jul 1999 10:56:25 -0700 (PDT) Message-Id: <199907291756.KAA00408@lestat.nas.nasa.gov> To: Matthew Dillon Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: MADV_SEQUENTIAL and GNU Grep Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 29 Jul 1999 10:56:24 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jul 1999 10:52:02 -0700 (PDT) Matthew Dillon wrote: > Yes, we already do this, but only for OBJT_DEFAULT and OBJT_SWAP objects. > We do not do this for file objects... it would make me rather nervous > if we did :-) Why? I can think of at least one instance where this is useful: using a file in the file system as a shared memory handle. Seems as if the programmer erroneously MADV_FREE's a file, well ... you only supplied the rope. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message