[lkml]   [2000]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Addressing logically the buffer cache
Juan <> writes:

> Alexander Viro escribió:
> >
> > On Tue, 14 Nov 2000, Juan wrote:
> >
> > > Hi!.
> > >
> > > Is there any patch or project to address logically the buffer cache?.
> > > Now, you use three parameters to find a buffer in cache: device, block
> > > number, and block size. But, what about if I want to find a buffer using
> > > a super block, an inode number, and a block number within the file
> > > specified by the inode number.
> >
> > What's wrong with using the pagecache and per-page buffer_heads?
> Suppose you are implementing a log-structured file system and a process
> adds a new logical block to a file. Besides, suppose that the segment is
> 512 KBytes in size. Usually, you don't want to write the segment before
> it is full. The logical block hasn't got a physical address because you
> don't build the segment until it is written to disk. So, what happens if
> another process wants to access to the new block?.
> You can't assign a physical address to the new block because the address
> can change when the buffer is written to disk.

So you don't assign a buffer head until you make the final decision.
There are some interesting issues with how you track that your data
is dirty but otherwise all is well.
> Perhaps, I'm wrong, but I think that the implementation of the BSD-LFS
> needs to address logically the buffer cache.

The linux vfs is quite different from the berkley one. The linux page
cache is much closer to the berkley block cache, then the depricated
linux block cache.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.065 / U:2.472 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site