From: "Francis Moreau" <francis.moro@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: question about splice performance
Date: Mon, 26 May 2008 10:57:54 +0200 [thread overview]
Message-ID: <38b2ab8a0805260157k14d9a64dkeef48d230b978cf4@mail.gmail.com> (raw)
In-Reply-To: <4839D05C.4040309@garzik.org>
Hello,
On Sun, May 25, 2008 at 10:47 PM, Jeff Garzik <jeff@garzik.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...
Also splice-cp uses 2 calls to splice syscall in a loop. So it end up doing a
lot of syscalls. Maybe using sendfile instead of is better.
Also2, since splice is a generalized pipe, it might be better to create to
processes, one writing to the pipe and the other one reading to have better
workflow.
That said I also see some use cases where splice could be more useful,
specially when one of the file descriptor is actually a device: one the write
side of the pipes a device could write some data while on the other side of
the pipe a process can empty the pipe by writing the data to a file.
Are there any plans to improve splice interface to be used by drivers ?
Thanks.
--
Francis
next prev parent reply other threads:[~2008-05-26 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 15:12 Francis Moreau
2008-05-25 15:40 ` Jan Engelhardt
2008-05-25 17:22 ` Sitsofe Wheeler
2008-05-25 20:47 ` Jeff Garzik
2008-05-26 8:57 ` Francis Moreau [this message]
2008-05-26 9:06 ` Bernd Petrovitsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38b2ab8a0805260157k14d9a64dkeef48d230b978cf4@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®