From owner-cvs-all Mon May 27 6:51:40 2002 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D766637B406; Mon, 27 May 2002 06:51:34 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g4RDoXpA049186; Mon, 27 May 2002 15:50:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/md md.c In-Reply-To: Your message of "Mon, 27 May 2002 23:50:49 +1000." <20020527232624.F16465-100000@gamplex.bde.org> Date: Mon, 27 May 2002 15:50:33 +0200 Message-ID: <49185.1022507433@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020527232624.F16465-100000@gamplex.bde.org>, Bruce Evans writes: >> Eventually this will allow us to test the 64bit cleanness of the disk >> I/O patch, but more work is outstanding here and elsewhere. > >Vnode-backed devices can already be used for this: > > dd if=/dev/zero of=zz bs=8k oseek=1073741822 count=1 > >on an 8K/1TB ffs filesystem gives an file of size (8TB - epsilon). Right, but this requires much more code to be correct than the simpler case of malloc backing. Once we have malloc backing 64bit correct we can take on this much harder test. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message