From owner-freebsd-arch Tue Jan 15 12:43:28 2002 Delivered-To: freebsd-arch@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 1081F37B419 for ; Tue, 15 Jan 2002 12:43:19 -0800 (PST) Received: from dialup-209.244.107.183.dial1.sanjose1.level3.net ([209.244.107.183] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16QaOM-0006Mo-00; Tue, 15 Jan 2002 12:41:10 -0800 Message-ID: <3C4493E3.5E322D19@mindspring.com> Date: Tue, 15 Jan 2002 12:41:07 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Max Khon , arch@FreeBSD.ORG Subject: Re: request for review References: <19068.1011092026@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I think it is bogus for devices other than disks to flout a > va_blocksize, but I am on the other hand not sure what the > relevant (if any) standards say. > > If this patch makes things better, I'm all for it. Ugh. Hard call. I agree with you in principle, but looking at the "stat(2)" man page: u_int32_t st_blksize; /* optimal blocksize for I/O */ Sort of implies that you'll get useful information back for anything. For regular files, you'd expect this to be the FS block size, almost... 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message