filesystems...

filesystems...

[Jure Menart]

Hello everyone...
me and some friends are making some motherboard with ppc4xx and other stuff,
well, that's not really that important... what matter is, that we have (only?)
16Mb of RAM. Now I'm trying to find appropriate software and modified it if
necessary.
Well, I was looking for some filesystems and found out that xfs and reiserfs
are pretty suitable, the only thing I'm worry about is our RAM. As I read in
documents they need more RAM than it is available. So question is... is there
anyone who successfully used XFS of ReiserFS on that amount of RAM, or is
there any other appropriate FS which is not so 'hungry' (we would need at
lease journaling system).

Thanks for all answers.

Best whishes, Jure Menart


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

filesystems

[Joe Harrington]

Does a typical Linux system or Mandrake boot using the ext2 filesystem? Do
all filesystems have or use commands such as stat, read, write and chmod. I
am trying to figure out without looking through the code how a VFS
filesystem works. I am assuming that it does not use the major minor system,
for faster access to data? On my system I have:

            ext2
            msdos
nodev proc

Yes I did a man filesystems, man virtual filesystems, and manVFS. What does
the nodev stand for? I have seen other systems containing filesystems such
as:

            ext2
            minix
            msdos
            vfat
nodev proc
nodev nfs
            iso9660
            ufs
nodev autofs
nodev devpts

Basically, do you mount a VFS filesystem, does it keep pages in RAM longer
than other filesystems. How would a VFS filesystem handle system calls such
as "stat" or "open"? I am just looking for something that can easily help me
visualize the VFS process.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: filesystems

[Tigran Aivazian]

On Wed, 22 Nov 2000, Joe Harrington wrote:

> Does a typical Linux system or Mandrake boot using the ext2 filesystem? Do
> all filesystems have or use commands such as stat, read, write and chmod. I
> am trying to figure out without looking through the code how a VFS
> filesystem works. I am assuming that it does not use the major minor system,
> for faster access to data? On my system I have:
> 
>             ext2
>             msdos
> nodev proc
> 
> Yes I did a man filesystems, man virtual filesystems, and manVFS. What does
> the nodev stand for? I have seen other systems containing filesystems such

nodev means the filesystem is not of type FS_REQ|UIRES_DEV, i.e. does not
require a block device to be mounted. In folklore, such are sometimes
called "virtual" filesystems. Examples are sockfs, shm, pipefs, proc, nfs,
devpts.


> as:
> 
>             ext2
>             minix
>             msdos
>             vfat
> nodev proc
> nodev nfs
>             iso9660
>             ufs
> nodev autofs
> nodev devpts
> 
> Basically, do you mount a VFS filesystem, does it keep pages in RAM longer
> than other filesystems.

you do not mount a VFS filesystem. VFS is not a filesystem. VFS is a
Virtual Filesystem Switch, i.e. a set of concepts, philosophy, data
structures and functions which together make writing new filesystems easy.
The name is derived from the SVR4 data structure vfssw (sic?) whence all
the good concepts of VFS came (yea, yea, I know, AV (and history books)
will tell me that Sun had a vnode/vfs layer and that even FreeBSD has a
sort of VFS/vnode layer but we all know that the really good form of VFS
came from SVR4, like it or not, the others, except Linux of course, are
impostors)


> How would a VFS filesystem handle system calls such
> as "stat" or "open"? I am just looking for something that can easily help me
> visualize the VFS process.

when doing stat system call, the VFS does a name lookup which causes the
relevant inode to be read from disk (by means of s_op->read_inode method
the filesystem registered) and so, all the relevant information is already
there in the incore inode, which is then copied to userspace.

You cannot visualize VFS without looking at the source code. In fact, you
cannot even do so by looking at the source, it is so complex. But it is
definitely worth a try -- just remember, it is a lifelong process.
Nevertheless, it is certainly a good thing to dedicate whole life to study
the subject so complex, and which changes so frequently that nobody in the
whole world has an overall picture of it. But we all try :) One day, we
will understand it all and rewrite it to be even better than it is now :)

Regards,
Tigran

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: filesystems

[Tigran Aivazian]

On Wed, 22 Nov 2000, Tigran Aivazian wrote:
> you do not mount a VFS filesystem. VFS is not a filesystem. VFS is a
> Virtual Filesystem Switch, i.e. a set of concepts, philosophy, data
> structures and functions which together make writing new filesystems easy.
> The name is derived from the SVR4 data structure vfssw (sic?) whence all
> the good concepts of VFS came (yea, yea, I know, AV (and history books)
> will tell me that Sun had a vnode/vfs layer and that even FreeBSD has a
> sort of VFS/vnode layer but we all know that the really good form of VFS
> came from SVR4, like it or not, the others, except Linux of course, are
> impostors)

perhaps I invented a new English word "achronal impostor", i.e. impostor
even if he was there before others ;)

And, to emphasize my respect to Al Viro, I would like to explain that I
sometimes spell "my personal humble opinion" as "we all know", just read
between the lines and you will be Ok.

Regards,
Tigran

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/