9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
To: 9fans@cse.psu.edu
Subject: [9fans] sendfile interface
Date: Thu, 20 Feb 2003 01:32:04 +0300	[thread overview]
Message-ID: <20030220013204.A6122@unicorn.math.spbu.ru> (raw)

While studying how Linux implements sendfile(2), I couldn't help
but notice, that it is yet another hack a'la mmap. "There must
be a better way to do that" I though at the moment.

Now, I imagine, that for Plan9 there should be no problem telling
kernel that one Chan should server as an "alias", or proxy if you
will, for another one. By doing that, it should be possible to
eliminate the whole "copy to userland buffer; copy back to kernel"
routine and it could be even possible to utilize hardware
scattered-write. How easy it will be for network connections ? Or may
be I'm stretching my imagination too far, and there's no really
a better way to do it. Please comment.

Thanks,
Roman.


             reply	other threads:[~2003-02-19 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 22:32 Roman V. Shaposhnick [this message]
2003-02-24  3:50 ` Roman V. Shaposhnick
2003-02-24  3:56   ` rob pike, esq.
2003-02-24  4:03   ` Russ Cox

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=20030220013204.A6122@unicorn.math.spbu.ru \
    --to=vugluskr@unicorn.math.spbu.ru \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).