From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Francis Moreau <francis.moro@gmail.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to avoid data copies in a driver ?
Date: Fri, 16 May 2008 09:10:19 +0100 [thread overview]
Message-ID: <482D416B.8060501@goop.org> (raw)
In-Reply-To: <38b2ab8a0805150040s6933de14p7c2014945ba0810d@mail.gmail.com>
Francis Moreau wrote:
> I'm suprised because what I need doens't seem so uncommon, usually
> devices send or
> receive data to/from files. So a helper (system call ?) to achieve
> that other than the basic
> read/write seems needed, no ?
>
It's fairly rare to have an application which requires moving data to
file with absolutely no processing; normally there's at least a bit of
massaging/parsing/etc. If that's really what you want to do, maybe you
can do it with splice? I haven't looked at it at all, but the intention
is that you can splice file descriptors together, so you can splice your
device fd to a file fd and have it all just work...
Alternatively you could read() from your device into a mmaped file.
That's a single copy from device to file, which is about the best you
can do without going to heroic lengths.
Also, it really depends on your application. Is it a high-bandwidth
thing in which the copy is a huge cost? Or do you want to eliminate the
copies because it seems like a nice thing to do?
J
next prev parent reply other threads:[~2008-05-16 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 19:54 How to avoid data copies in a driver ? Francis Moreau
2008-05-14 20:02 ` Lennart Sorensen
2008-05-15 7:44 ` Francis Moreau
2008-05-15 13:59 ` Lennart Sorensen
2008-05-16 20:17 ` Francis Moreau
2008-05-14 21:23 ` linux-os (Dick Johnson)
2008-05-15 7:40 ` Francis Moreau
2008-05-15 11:50 ` Arnd Hannemann
2008-05-15 12:08 ` Francis Moreau
2008-05-15 13:16 ` linux-os (Dick Johnson)
2008-05-16 8:10 ` Jeremy Fitzhardinge [this message]
2008-05-16 11:44 ` Francis Moreau
2008-05-21 10:41 ` Pavel Machek
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=482D416B.8060501@goop.org \
--to=jeremy@goop.org \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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.