From owner-freebsd-hackers Wed Aug 11 11:23: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 6A80F14E17 for ; Wed, 11 Aug 1999 11:22:56 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA26998; Wed, 11 Aug 1999 11:19:06 -0700 (PDT) Message-Id: <199908111819.LAA26998@implode.root.com> To: Charles Randall Cc: freebsd-hackers@FreeBSD.ORG, Oleg Derevenetz Subject: Re: mmap bug In-reply-to: Your message of "Wed, 11 Aug 1999 11:56:39 MDT." <64003B21ECCAD11185C500805F31EC0303786B72@houston.matchlogic.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Aug 1999 11:19:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Looks like Oleg made a mistake in posting the code. I saw an earlier version >of this in freebsd-questions and followed up with him. > >I've appended the version I think he meant to include. > >He's reporting this behavior with 3.2R. Runs fine with 'mmap -u', appears to >hang the machine on the second iteration (file "1") with 'mmap'. > >Runs fine on Solaris 2.6 and Digital Unix 4.0D -- with the exception of >filling the disk without "-u" :^). > >He's trying to ask if this is a problem with the code in question or 3.2R's >mmap. That's better. It appears to be a classic resource related deadlock that is caused by the VFS code needing pages in order to page things out (and thus free up pages), but is unable to since no memory is available. Matt Dillon was working on deadlocks like this in -current awhile back and it would be interesting to know if the hang occurs there as well. I don't have a -current machine at the moment so I can't test it myself. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message