> >+config AZ_FS
> >+ tristate "AZFS filesystem support"
>
> This is slightly redundant, it should probably be
> tristate "AZ filesystem support"
I have called it the same way as other file systems (in Kconfig they say "JFS filesystem support", "XFS filesystem support", "NTFS file system support", ...)
> >+ help
> >+ azfs is a file system for I/O attached memory backing. It requires
> >+ a block device with direct_access capability, e.g. axonram.
>
> (a) What is axonram?
> (b) why is axonram direct_access, and my other devices (including
> standard PC RAM) not?
Axonram is a module specific for IBM CellBlade and allows access to a DDR2 memory attached onto Axon controller.
You don't need direct_access and not azfs for main memory because there is already a pretty nice tmpfs for it.
> >+ Mounting such device with azfs gives memory mapped access to the
> >+ underlying memory to user space.
>
> Can't I just mmap(/dev/theblockdevice), why would I need to go through
> azfs?
Yes, you can mmap it. But what does it have to do with a file system. I would say you can either mmap it or place a file system on it.
--
Mit freundlichen Grüßen / met vriendelijke groeten / avec regards
Maxim V. Shchetynin
Linux Kernel Entwicklung
IBM Deutschland Entwicklung GmbH
Linux für Cell, Abteilung 3250
Schönaicher Straße 220
71032 Böblingen
Vorsitzender des Aufsichtsrats: Johann Weihen
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registriergericht: Amtsgericht Stuttgart, HRB 243294
Fahr nur so schnell wie dein Schutzengel fliegen kann!
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
