From owner-freebsd-hackers Thu Aug 27 09:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02543 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 09:21:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02538 for ; Thu, 27 Aug 1998 09:21:07 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA11187 for ; Thu, 27 Aug 1998 12:20:14 -0400 (EDT) Date: Thu, 27 Aug 1998 12:20:14 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: FFS questions 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 I am reading the source code in fs.h and the parameter fs_cpc confuses me. The comment says it is the number of cylinders per *cycle* in position table. What does the "cycle" mean? Basically the position table is used to space out contiguous logical blocks on the disk so that when the disk head moves to the next block, CPU has already initiates a new transfer request for exactly that block. But how can we measure the time it takes CPU (time-sharing by processes) to service an interrupt and initiate a new I/O? Is the disk always moving around at constant speed? When does the disk generate an interrupt? After it finish DMA a block or a sequence of contiguous blocks specified by the CPU's request? 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