From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Zero copy between ISR, kernel and User
Date: Wed, 27 Sep 2006 12:10:30 -0700 [thread overview]
Message-ID: <20060927121030.4469ec6e@freekitty> (raw)
In-Reply-To: 4519F7A9.4050807@saville.com
On Tue, 26 Sep 2006 21:01:45 -0700
Wink Saville <wink@saville.com> wrote:
> Hello,
>
> I would like to allow the transferring of data between ISR's, kernel and
> user code, without requiring copying. I envision allocating buffers in
> the kernel and then mapping them so that they appear at the same
> addresses to all code, and never being swapped out of memory.
>
> Is this feasible for all supported Linux architectures and is there
> existing code that someone could point me towards?
>
> Regards,
>
> Wink Saville
>
Your better off having application mmap a device, then transfer
the data to there. Something like AF_PACKET.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-09-27 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 4:01 Zero copy between ISR, kernel and User Wink Saville
2006-09-27 19:10 ` Stephen Hemminger [this message]
2006-09-28 14:45 ` Wink Saville
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=20060927121030.4469ec6e@freekitty \
--to=shemminger@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox