From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Subject: Re: splice() on two pipes
Date: Wed, 29 Apr 2009 17:23:05 +0200 [thread overview]
Message-ID: <87my9zpjqe.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090429103308.GA23684@squirrel.roonstrasse.net> (Max Kellermann's message of "Wed, 29 Apr 2009 12:33:08 +0200")
Max Kellermann <max@duempel.org> writes:
I don't think splice is about handling all possible cases,
but just cases where the kernel can do better than user space.
I don't think that's the case here.
> when I read about the splice() system call, I thought it was obvious
> that it could copy data between two pipes.
It would be more efficient if you used fd passing to pass the fd
around to the other process and let it read directly.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-29 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 10:33 splice() on two pipes Max Kellermann
2009-04-29 15:23 ` Andi Kleen [this message]
2009-04-29 19:42 ` Max Kellermann
2009-04-30 4:56 ` Willy Tarreau
2009-04-30 14:26 ` Mark Hills
2009-04-30 6:21 ` Jens Axboe
2009-04-30 6:42 ` Max Kellermann
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=87my9zpjqe.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.