From: Jamie Lokier <jamie@shareable.org>
To: Mark Borgerding <mark@borgerding.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: idea: user to user pipe copy
Date: Fri, 23 Apr 2004 15:29:37 +0100 [thread overview]
Message-ID: <20040423142937.GA6300@mail.shareable.org> (raw)
In-Reply-To: <40884D88.90408@borgerding.net>
Mark Borgerding wrote:
> Why not keep track of blocked read()s on a pipe fd?
>
> When the writer writes something to the pipe, data could be copied
> directly from one user process to another, rather than
> calling copy_from_user then copy_to_user.
>
> This alleged speed increase would benefit all blocking pipes & fifos,
> roughly half the time (i.e. whenever the read happens before the write).
You only get page faults from one of the mm contexts, so
copy_from_user_to_other_user would have to do explicit page table
operations to find the pages of the other mm. There may also be
a little data cache flushing required with SMP.
It seems feasible.
-- Jamie
next prev parent reply other threads:[~2004-04-23 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 22:56 idea: user to user pipe copy Mark Borgerding
2004-04-23 11:46 ` Mark Borgerding
2004-04-23 14:29 ` Jamie Lokier [this message]
2004-04-23 16:27 ` Bryan Henderson
2004-04-23 19:26 ` Mark Borgerding
2004-04-23 20:40 ` Bryan Henderson
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=20040423142937.GA6300@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark@borgerding.net \
/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.