From owner-freebsd-hackers Wed Mar 22 17:41:22 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA22528 for hackers-outgoing; Wed, 22 Mar 1995 17:41:22 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA22521 for ; Wed, 22 Mar 1995 17:41:21 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA15550; Wed, 22 Mar 95 18:34:54 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503230134.AA15550@cs.weber.edu> Subject: Re: Why IDE is bad To: toor@jsdinc.root.com (John S. Dyson) Date: Wed, 22 Mar 95 18:34:54 MST Cc: star-gate.com!hasty@implode.root.com, hackers@FreeBSD.org In-Reply-To: <199503221959.TAA00296@jsdinc.root.com> from "John S. Dyson" at Mar 22, 95 07:59:28 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Is only 5 secondes faster... > > > I believe that async mounts are essentially unimplemented in UFS??? What do you mean "async mounts"? Since kernel entry via system call is atomic unless you have SMP or multithreading to support multiple kernel thread contexts, it really can't be anything but synchronous. A UFS mount in the kernel goes to the device, reads the volume header and superblock into core, gets a vnode for inode 2, and arranges to have references to the vnode in the file system it is mounted into return vnode 2 of the mounted fs. Then it returns from the mount call. This is synchronous, but it is also guaranteed to be deterministically quick, by definition. Am I missing something about what you mean when you say "async mounts"? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.