From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Jelle Foks <jelle@flying.demon.nl>
Cc: linux-mm@kvack.org
Subject: Re: I/O and MM question
Date: Mon, 11 Jan 1999 00:52:18 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.04.9901110047460.29777-100000@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.03.9901101752050.13236-100000@zap.zap>
On Sun, 10 Jan 1999, Jelle Foks wrote:
> (how/which function to use?). Does the mm/paging system of Linux allow me
> this? Or does the mm/paging code already somehow eliminate the memory-copy
> of the fread()->fwrite() combo (how?)?
What about sendfile(2) ? It's linux-sepcific, but it does avoid
the getuser/putuser-couple for the data to be read/written.
cu
Ingo
--
Feel the power of the penguin - run linux@your.pc
<esc>:x
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
prev parent reply other threads:[~1999-01-10 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-10 17:13 Jelle Foks
1999-01-10 23:52 ` Ingo Oeser [this message]
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=Pine.LNX.4.04.9901110047460.29777-100000@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=jelle@flying.demon.nl \
--cc=linux-mm@kvack.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