>
> > The big benefits to locality of meta & file data are to allow
> > drive/driver caching to do sequential (or close to) reads in as large
> > blocks as possible. There was a recent SigOS paper on a modified Unix
> > filesystem that was designed to take advantage of modern disk systems,
>
> The big benefits to locality of meta & file data are to allow
> drive/driver caching to do sequential (or close to) reads in as large
> blocks as possible. There was a recent SigOS paper on a modified Unix
> filesystem that was designed to take advantage of modern disk systems,
Do you st
Matthew Dillon <[EMAIL PROTECTED]> writes:
>:> distribute the inodes all over the cylinder group rather then concentrate
>:> all the inodes in one place.
>:
>:Yes. I have implemented most of the code. I noticed the "ls -al" is slow
>:but "ls" is OK.
>
>Yes, ls (without any options) is ok bec
Matthew Dillon <[EMAIL PROTECTED]> writes:
>:On Mon, 6 Dec 1999, Zhihui Zhang wrote:
>:> I have modified FFS filesystem code to put the disk inode at the beginning
>:> of a file, i.e, the logical block #0 of each file begins with 128 bytes of
>:> its disk inode and the rest of it are file data.
>
:> distribute the inodes all over the cylinder group rather then concentrate
:> all the inodes in one place.
:
:Yes. I have implemented most of the code. I noticed the "ls -al" is slow
:but "ls" is OK.
Yes, ls (without any options) is ok because the file type is now being
stuffe
On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
> On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> > I am doing some research on filesystem. I guess it may be faster to put
> > the disk inode with its file data together so that both can be read into
> > memory in one I/O.
>
> I still don't get it. To g
In message <[EMAIL PROTECTED]>, "Ronal
d G. Minnich" writes:
>On Mon, 6 Dec 1999, Zhihui Zhang wrote:
>> I am doing some research on filesystem. I guess it may be faster to put
>> the disk inode with its file data together so that both can be read into
>> memory in one I/O.
>
>I still don't get
On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> I am doing some research on filesystem. I guess it may be faster to put
> the disk inode with its file data together so that both can be read into
> memory in one I/O.
I still don't get it. To get the file, you do a lookup. So the inode is in
memory. Th
On Mon, 6 Dec 1999, Matthew Dillon wrote:
> :On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
> :
> :> On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> :> > I have modified FFS filesystem code to put the disk inode at the beginning
> :> > of a file, i.e, the logical block #0 of each file begins with 128 b
On Mon, 6 Dec 1999, Julian Elischer wrote:
> how do you find the inode?
There is an inode address map to look up. Each entry is four bytes.
-Zhihui
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 6 Dec 1999, Matthew Dillon wrote:
> :On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
> :
> :> On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> :> > I have modified FFS filesystem code to put the disk inode at the beginning
> :> > of a file, i.e, the logical block #0 of each file begins with 128 by
how do you find the inode?
On Mon, 6 Dec 1999, Zhihui Zhang wrote:
>
> On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
>
> > On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> > > I have modified FFS filesystem code to put the disk inode at the beginning
> > > of a file, i.e, the logical block #0 of eac
:On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
:
:> On Mon, 6 Dec 1999, Zhihui Zhang wrote:
:> > I have modified FFS filesystem code to put the disk inode at the beginning
:> > of a file, i.e, the logical block #0 of each file begins with 128 bytes of
:> > its disk inode and the rest of it are file
:On Mon, 6 Dec 1999, Zhihui Zhang wrote:
:> I have modified FFS filesystem code to put the disk inode at the beginning
:> of a file, i.e, the logical block #0 of each file begins with 128 bytes of
:> its disk inode and the rest of it are file data.
:
:first question I have is, why?
:
:ron
Go
On Mon, 6 Dec 1999, Ronald G. Minnich wrote:
> On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> > I have modified FFS filesystem code to put the disk inode at the beginning
> > of a file, i.e, the logical block #0 of each file begins with 128 bytes of
> > its disk inode and the rest of it are file data
On Mon, 6 Dec 1999, Zhihui Zhang wrote:
> I have modified FFS filesystem code to put the disk inode at the beginning
> of a file, i.e, the logical block #0 of each file begins with 128 bytes of
> its disk inode and the rest of it are file data.
first question I have is, why?
ron
To Unsubscri
I have modified FFS filesystem code to put the disk inode at the beginning
of a file, i.e, the logical block #0 of each file begins with 128 bytes of
its disk inode and the rest of it are file data.
Everything seems to be working. But I am stuck with an ELF executable
file stored in this layou
17 matches
Mail list logo
