From: Mark Borgerding <mark@borgerding.net>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Jamie Lokier <jamie@shareable.org>, linux-fsdevel@vger.kernel.org
Subject: Re: idea: user to user pipe copy
Date: Fri, 23 Apr 2004 15:26:33 -0400 [thread overview]
Message-ID: <40896DE9.80303@borgerding.net> (raw)
In-Reply-To: <OFE456E79B.9EEA4C89-ON88256E7F.00592FDE-88256E7F.005A69B8@us.ibm.com>
Jamie & Bryan,
Thanks for your input on the user-to-user copy problem. I won't pretend
to understand all the issues of which you speak.
Are these issues insurmountable? Is it worth it? Would the extra
complexity of the user-user copy add security holes and stability problems?
If someone were willing to work on copy_user_to_other_user, I could
manage the pipe work.
Anyone feel like battling that windmill?
Eliminating one out of two buffer copies is a fine and noble goal.
Something you can brag to your grandkids about ;)
BTW, it seems this could make unix sockets faster too.
-- Mark
next prev parent reply other threads:[~2004-04-23 19:26 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
2004-04-23 16:27 ` Bryan Henderson
2004-04-23 19:26 ` Mark Borgerding [this message]
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=40896DE9.80303@borgerding.net \
--to=mark@borgerding.net \
--cc=hbryan@us.ibm.com \
--cc=jamie@shareable.org \
--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.