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.0806171634040.32473@fbirervta.pbzchgretzou.qr>
Date:	Tue, 17 Jun 2008 16:36:28 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Maxim Shchetynin <maxim@...ux.vnet.ibm.com>
cc:	linux-fsdevel@...r.kernel.org, Matthew Wilcox <matthew@....cx>,
	linux-kernel@...r.kernel.org
Subject: Re: AZFS file system proposal


On Tuesday 2008-06-17 13:57, 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...?
>
>The "?" at the end of your sentence might mean a question. I would
>be really happy to give an answer on it if I could understand it.

If one does not need direct_access nor azfs, and ext2 plus XIP minus
caching or tmpfs plus XIP can achieve the same effect, what can azfs
that we could not already do without 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/