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]

Message-ID: <20080315133242.GB4828@ucw.cz>
Date:	Sat, 15 Mar 2008 14:32:42 +0100
From:	Pavel Machek <pavel@....cz>
To:	Daniel Phillips <phillips@...nq.net>
Cc:	David Newall <davidn@...idnewall.com>,
	Chris Friesen <cfriesen@...tel.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Ramback: faster than a speeding bullet

On Wed 2008-03-12 22:50:55, Daniel Phillips wrote:
> On Wednesday 12 March 2008 23:30, David Newall wrote:
> > Daniel Phillips wrote:
> > >> Your idea seems predicated on throwing large amounts of RAM at the
> > >> problem.  What I want to know is this: Is it really 25 times faster than
> > >> ext3 with an equally huge buffer cache?
> > >
> > > Yes.
> > 
> > Well, that sounds convincing.  Not.  You know this how?
> 
> By measuring it.  time untar -xf linux-2.2.26.tar; time sync

Thats cheating. Your ramback ignores sync.

Just time it against ext3 _without_ doing the sync. That's still more
reliable than what you have.

Heck, comment out sync and fsync from your kernel. You'll likely be 10
times normal speed, and still more reliable than ramback.
							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/