All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Borgerding <mark@borgerding.net>
To: linux-fsdevel@vger.kernel.org
Subject: idea: user to user pipe copy
Date: Thu, 22 Apr 2004 18:56:08 -0400	[thread overview]
Message-ID: <40884D88.90408@borgerding.net> (raw)

Would someone tell me why this
a) won't work?
b) shouldn't be done?
c) is the dumbest idea since Microsoft Bob?


Currently, piped data gets copied from user space to a kernel buffer 
then back out to user space. 

This happens regardless of whether there is already a reader who is 
blocked on that fd.

Instead ...

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).

-- Mark Borgerding


             reply	other threads:[~2004-04-22 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 22:56 Mark Borgerding [this message]
2004-04-23 11:46 ` idea: user to user pipe copy Mark Borgerding
2004-04-23 14:29 ` Jamie Lokier
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=40884D88.90408@borgerding.net \
    --to=mark@borgerding.net \
    --cc=linux-fsdevel@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.