linux-ext4 - Re: Atomic non-durable file write API

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: <AANLkTikW8K4VFLJuYngU64m2vAL1yhA3R=jRt7U6-RRp@mail.gmail.com>
Date:	Tue, 28 Dec 2010 18:22:42 +0100
From:	Olaf van der Spek <olafvdspek@...il.com>
To:	Christian Stroetmann <stroetmann@...olinux.com>
Cc:	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-ext4@...r.kernel.org, "Ted Ts'o" <tytso@....edu>,
	Nick Piggin <npiggin@...il.com>
Subject: Re: Atomic non-durable file write API

On Mon, Dec 27, 2010 at 8:30 PM, Christian Stroetmann
<stroetmann@...olinux.com> wrote:
> Btw.: There is even no analogy: "The concepts are the same".

So? Doesn't mean you implement full ACID DB-like transactions.

>>>> Still waiting on any hint for why that performance loss would happen.
>>>
>>> > From my point of view, the loss of performance depends on what is
>>> benchmarked in which way.
>>
>> Maybe, but still no indication of why.
>
> If you have a solution, then you really should show other persons the
> working source code.

I don't have source code.
Are you not capable of reasoning about something without having
concrete source code?

> For me speaking: I like such technologies and I'm also interested in your
> attempts.

Writing code is a lot of work and one should have the design clear
before writing code, IMO.

Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html