Re: AZFS file system proposal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 2008-06-17 11:06, Maxim Shchetynin wrote:
>
>> (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.

So the reason azfs could be useful is...?

>> >+         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.

Exactly, that's what I was asking myself.

>I would say you can either mmap it or place a file system on it.

The help text implies that I *need* azfs to mmap it - and that sounds
like a Rube Goldberg machine.
--
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

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux