From: Robert Hancock <hancockr@shaw.ca>
To: Martin Drab <drab@kepler.fjfi.cvut.cz>,
hugh@veritas.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question about memory mapping mechanism
Date: Thu, 08 Mar 2007 18:35:55 -0600 [thread overview]
Message-ID: <45F0ABEB.3030201@shaw.ca> (raw)
In-Reply-To: <fa.8Fy6n0Le4Y2mDfeEy936/5bbJHA@ifi.uio.no>
Martin Drab wrote:
> Hi,
>
> I'm writing a driver for a sampling device that is constantly delivering a
> relatively high amount of data (about 16 MB/s) and I need to deliver the
> data to the user-space ASAP. To prevent data loss I create a queue of
> buffers (consisting of few pages each) which are more or less directly
> filled by the device and then mapped to the user-space via mmap().
>
> The thing is that I'd like to prevent kernel to swap these pages out,
> because then I may loose some data when they are not available in time
> for the next round.
It would likely be easier to just mlock this buffer from the userspace
application, rather than trying to achieve this in the driver..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-03-09 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.8Fy6n0Le4Y2mDfeEy936/5bbJHA@ifi.uio.no>
2007-03-09 0:35 ` Robert Hancock [this message]
2007-03-09 0:52 ` Question about memory mapping mechanism Martin Drab
2007-03-08 13:16 Martin Drab
2007-03-08 14:20 ` Carsten Otte
[not found] ` <5c77e7070703080617r63cbccfevd2c6d678f16c2b03@mail.gmail.com>
2007-03-08 21:36 ` Martin Drab
2007-03-09 0:07 ` Martin Drab
2007-03-09 1:31 ` Martin Drab
2007-03-13 20:49 ` Hugh Dickins
2007-05-21 18:39 ` Martin Drab
2007-05-29 17:58 ` Hugh Dickins
2007-03-08 23:21 ` Martin Drab
2007-03-09 0:27 ` Jeremy Fitzhardinge
2007-03-09 0:38 ` Martin Drab
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=45F0ABEB.3030201@shaw.ca \
--to=hancockr@shaw.ca \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=hugh@veritas.com \
--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