linux-kernel - Re: question about splice performance

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] [day] [month] [year] [list]

Message-Id: <1211792801.2052.14.camel@tara.firmix.at>
Date:	Mon, 26 May 2008 11:06:41 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	jens.axboe@...cle.com
Subject: Re: question about splice performance

Hi!

On Mon, 2008-05-26 at 10:57 +0200, Francis Moreau wrote:
> On Sun, May 25, 2008 at 10:47 PM, Jeff Garzik <jeff@...zik.org> wrote:
> >
> > If you drop caches you are not measuring splice speed.
> >
> > Use ramfs for your tests (guarantees data is in cache) instead.
> 
> So it seems that the gain when using splice to copy a file into another file
> is very limited. Maybe that's the reason why cp is still using read/write...

To point it out one more time: If you copy from one file on a physical
harddisk (or more or less similar hardware) to another (with cold
caches), the bottleneck is most probably the harddisk.

splice() simply reduces the amount of copied data in the RAM - and that
is practically irrelevant if you read and write to and from harddisks.

So if you want to measure the savings of using splice() (instad of
read()/write(), etc.): Copy to and from RAM disks (and thus rule out the
slow hardware).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


--
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/