From owner-freebsd-current  Tue May 13 11:49:43 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA06240
          for current-outgoing; Tue, 13 May 1997 11:49:43 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06224
          for <freebsd-current@FreeBSD.ORG>; Tue, 13 May 1997 11:49:40 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.6.9) id NAA02084; Tue, 13 May 1997 13:49:24 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199705131849.NAA02084@dyson.iquest.net>
Subject: Re: Big problem with b_blkno
In-Reply-To: <19970513192351.KJ04154@ida.interface-business.de> from J Wunsch at "May 13, 97 07:23:51 pm"
To: joerg_wunsch@interface-business.de
Date: Tue, 13 May 1997 13:49:24 -0500 (EST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> As Doug Rabson wrote:
> 
> > NFS' use of b_blkno is about as bogus as it gets.  Have a look at
> > nfs_bmap for instance.  Actually, I think vfs_bio.c's habit of comparing
> > b_blkno to b_lblkno to decide whether it has called VOP_BMAP yet should
> > rank pretty highly on the bogus usage stakes.
> 
> :-)
> 
> Anyway, that doesn't bring us a single step further towards a solution
> of the original problem...  We simply can't live any longer with
> b_blkno being counted in terms of any predefined blocksiz.
>
I like the idea of the b_offset thing.  (I hate the idea of 64 bits
though, but them's the breaks.)

John