From owner-freebsd-hackers Mon Aug 10 12:28:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20204 for freebsd-hackers-outgoing; Mon, 10 Aug 1998 12:28:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20199 for ; Mon, 10 Aug 1998 12:28:27 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id PAA05095 for ; Mon, 10 Aug 1998 15:28:04 -0400 (EDT) Date: Mon, 10 Aug 1998 15:28:03 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Question about routine getblk() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, getblk() tries to get a buffer with specified size of physical memory allocated to it. I got two questions about this routine: (1) The given size could be greater than the optimial size contained in the mount structure. The comment says "this happens on mount points". Why is the case? (2) If the buffer is in the core, we check for size inconsistancies. Why should this happen and why should we be conservative on metadata. Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message