From: Xavier Roche <roche+kml2@exalead.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Inter-process send()/recv() using zero-copy ?
Date: Wed, 23 Sep 2009 08:01:27 +0200 [thread overview]
Message-ID: <4AB9B9B7.1020309@exalead.com> (raw)
Hi folks,
I was wondering if there was a way to have zero-copy send()/recv(), when
the socket is connected to the local machine (to another process on the
same machine, for example) ?
Such feature would be only feasible with page-aligned blocks, from an a
mmap'ed block to another one, I guess.
Typical case:
Process #1 (uid A)
buff = mmap(0, size, ..) /* anonymous or not */
...
send(s, buff, size, 0)
munmap(buff, size)
Process #2 (uid B)
buff = mmap(0, size, .. | MAP_ANONYMOUS, ..)
recv(s, buff, size, 0)
In an ideal fantasy world, the first process would use send() to
transmit the complete page-aligned memory block to the other side, and
the second process would use recv() to get the memory block on a similar
anonymously mmap'ed block, and the only operation the kernel would do
would be to share the memory block between the two processes with
copy-on-write.
On the real world, the same operation requires a first read of the whole
memory block (possibly partially on disk) and a complete write (possibly
partially on disk, too) with two copies of the same memory region at the
end.
Two solutions can be used to emulate such feature:
1. use a temporary mmap'ed file
- but requires a temporary file
- permissions for the file ? (not necessarily from the same UID)
- special case for local network block transmissions vs. machine-to-machine
2. use shared memory explicitely
- handling of permissions ? (ditto)
- special case for local network block transmissions vs. machine-to-machine
splice() and friends do not appear to give any help for this case, and I
was wondering if there was a chance to do that ?
next reply other threads:[~2009-09-23 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 6:01 Xavier Roche [this message]
2009-09-23 6:43 ` Inter-process send()/recv() using zero-copy ? Arjan van de Ven
2009-09-23 6:51 ` Nikita V. Youshchenko
2009-09-23 7:04 ` Xavier Roche
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=4AB9B9B7.1020309@exalead.com \
--to=roche+kml2@exalead.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