From: "Francis Moreau" <francis.moro@gmail.com>
To: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to avoid data copies in a driver ?
Date: Thu, 15 May 2008 09:44:37 +0200 [thread overview]
Message-ID: <38b2ab8a0805150044q3f336d64v20dd5ac78a2c1af2@mail.gmail.com> (raw)
In-Reply-To: <20080514200250.GB7579@csclub.uwaterloo.ca>
On Wed, May 14, 2008 at 10:02 PM, Lennart Sorensen
<lsorense@csclub.uwaterloo.ca> wrote:
> On Wed, May 14, 2008 at 09:54:03PM +0200, Francis Moreau wrote:
>> Hello,
>>
>> I'd like to optimize my driver, which receives data through a fifo and gives
>> them to a user space application. In turns this application moves this data
>> into a file.
>>
>> To avoid several useless copies, I'd like the application to pass to the driver
>> a file descriptor (?) to the driver and then the driver can directly move the
>> received data to that file.
>>
>> Could anybody give me some example of such scheme ?
>
> If the application memory mapped the file, would it be able to simply
> pass a pointer to that mapped file as part of the call to the driver and
> the driver would place the data directly at the requested location which
> would then be directly to the file?
>
So I would need to map this pointer into the kernel space, then fill it, take
care of cache coherency, unmap the kernel pointer.
Do you have any example of that in the kernel tree ?
BTW, data are received in interrupt context. Is it safe to put them in mapped
memory (can I have page fault ?) in this context ?
Thanks
--
Francis
next prev parent reply other threads:[~2008-05-15 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 19:54 Francis Moreau
2008-05-14 20:02 ` Lennart Sorensen
2008-05-15 7:44 ` Francis Moreau [this message]
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
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=38b2ab8a0805150044q3f336d64v20dd5ac78a2c1af2@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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
all inboxes | Powered by JetHome®