linux-kernel - Re: [ANNOUNCE] Ramback: faster than a speeding bullet

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]

Date:	Sun, 23 Mar 2008 10:33:46 +0100
From:	Pavel Machek <pavel@....cz>
To:	Daniel Phillips <phillips@...nq.net>
Cc:	David Newall <davidn@...idnewall.com>, david@...g.hm,
	Alan Cox <alan@...rguk.ukuu.org.uk>, Willy Tarreau <w@....eu>,
	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Ramback: faster than a speeding bullet

On Mon 2008-03-17 00:25:27, Daniel Phillips wrote:
> On Monday 17 March 2008 00:14, David Newall wrote:
> > >> if you are depending on replication over the network you have just limited 
> > >> your throughput to your network speed and latency.
> > >
> > > Replication does not work that way.  On each replication cycle, the
> > > differences between the most recent two volume snapshots go over the
> > > network. [...]
> > > Mirroring on the other hand, makes a realtime copy of a volume, that is
> > > never out of date.
> > 
> > I think you've just tried to obfuscate the truth.  As you have
> > described, replication does not provide full protection against data
> > loss; it loses all changes since last cycle.  Recall that it was you who
> > introduced the word "replication", in the context of guaranteeing no
> > loss of data.
> 
> You are twisting words.  I may have said that replication provides a
> point-in-time copy of a volume, which is exactly what it does, no more,
> no less.
> 
> > You still haven't investigated the benefit of your idea over a whopping
> > great buffer cache.  What's the point in all of this if it turns out, as
> > Alan hinted should be the case, that a big buffer cache gives much the
> > same performance?  You appear to have gone to a great deal of effort
> > without having performed quite simple yet obvious experiments.
> 
> A big buffer cache does not provide a guarantee that the dirty cache
> data saved to disk when line power is lost.  If you would like to

on_battery_power:

sync
mount / -oremount sync

...will of course work okay on any reasonable system. Not on yours,
because you have to do

echo i_really_mean_sync_when_i_say_sync > /hidden/file/somewhere
sync

(...which also shows that you are cheating).

Now, will you either do your homework and show that page cache is
somehow unsuitable for your job, or just stop wasting the bandwidth
with useless rants?
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/