From owner-freebsd-hackers Mon Jun 28 1:17:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id E6BFE14E12 for ; Mon, 28 Jun 1999 01:17:41 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 28 Jun 1999 10:20:40 +0200 Message-ID: <55586E7391ACD211B9730000C11002761796A9@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Matthew Dillon' , Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Implementation of mmap() in FreeBSD Date: Mon, 28 Jun 1999 10:14:50 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > :All these situations seem to me are not handled by FreeBSD mmap() > code. I > :hope I am wrong. I also wonder why we can not add some information to > the > > No machine's mmap() code handles these situations. It is a side > effect > of the way MMU's work and the way mmap() was defined - that is, in > order > for mmap() to be reasonably optimal it has to munge the boundry > conditions. It is an explicitly allowed case. > [ML] It is possible to handle these cases in VM code, by trapping on any access to the partial page, and allowing only those accesses which are withing the originally requested range. Performance would suck without end, though. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message