From owner-freebsd-fs Wed Jun 24 12:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09421 for freebsd-fs-outgoing; Wed, 24 Jun 1998 12:17:58 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09313 for ; Wed, 24 Jun 1998 12:17:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA02088; Wed, 24 Jun 1998 21:06:30 +0200 (CEST) To: Bruce Evans cc: fs@FreeBSD.ORG Subject: Re: lazy syncing of timestamps for special files In-reply-to: Your message of "Thu, 25 Jun 1998 02:02:34 +1000." <199806241602.CAA24267@godzilla.zeta.org.au> Date: Wed, 24 Jun 1998 21:06:28 +0200 Message-ID: <2086.898715188@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199806241602.CAA24267@godzilla.zeta.org.au>, Bruce Evans writes: >These changes implement delaying until vnode reclamation time of writing >timestamps for special files. This is most useful for preventing >disk activity on laptops just because something wrote to a terminal >(see PR5577 for a broken version). > >Please review. I think the first part of {ffs,ext2}_update() should be put in an ufs_update() function which is called from those two places. Otherwise that rather hairy bit of code is going to suffer from even more cut&paste deterioration in the future. Otherwise it looks good. I'll run it on my laptop and see if I notice anything... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message