From owner-freebsd-emulation Mon Jan 3 11:51:49 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id A8AFB14EA2; Mon, 3 Jan 2000 11:51:45 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id E6C73A84F; Mon, 3 Jan 2000 20:51:43 +0100 (CET) Date: Mon, 3 Jan 2000 20:51:43 +0100 From: Guido van Rooij To: Peter Wemm Cc: Hidetoshi Shimokawa , vsilyaev@mindspring.com, dillon@freebsd.org, freebsd-emulation@FreeBSD.ORG, dbutter@wireless.net Subject: Re: VMware: Questions... Message-ID: <20000103205143.A44784@gvr.gvr.org> References: <20000103192903.AEF531CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000103192903.AEF531CA0@overcee.netplex.com.au>; from Peter Wemm on Tue, Jan 04, 2000 at 03:29:03AM +0800 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 04, 2000 at 03:29:03AM +0800, Peter Wemm wrote: > > Heh, yours is simpler than mine. I was attempting a more generic solution > that marked a vnode as unlinked in the filesystems and the syncer then took > special care to avoid msyncing them. Mine would have caught the case where > a file was mmaped first then unlinked and kept open. If the syncer could Which is better then mine. > do anything special with unlinked plain files, it would then have the > information to deal with them too. (It doesn't, so that part is academic). > FFS already discards dirty blocks on last close if the file is already > unlinked. > I just committed my patch. If you think yours is better, feel free to back mine out. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message