linux-kernel - Re: AZFS file system proposal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.1.10.0806110000560.20733@fbirervta.pbzchgretzou.qr>
Date:	Wed, 11 Jun 2008 00:02:40 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Maxim Shchetynin <maxim@...ux.vnet.ibm.com>
cc:	Matthew Wilcox <matthew@....cx>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: AZFS file system proposal


On Tuesday 2008-06-10 10:49, Maxim Shchetynin wrote:
>
>What do you think about the following - shorter description and a better place for it (moved to "Pseudo filesystems"):
>
>--- linux-2.6.26-rc5/fs/Kconfig 2008-06-05 05:10:44.000000000 +0200
>+++ linux-2.6.26-rc5-azfs/fs/Kconfig    2008-06-10 10:43:24.326686538 +0200
>@@ -1017,6 +1017,19 @@
> config HUGETLB_PAGE
>        def_bool HUGETLBFS
>
>+config AZ_FS
>+       tristate "AZFS filesystem support"

This is slightly redundant, it should probably be
	tristate "AZ filesystem 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?

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


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