From: Benno Senoner <sbenno@gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: mmap() better than read() fro streaming, Was: Re: Streaming disk I/O kills file buffering and ma
Date: Wed, 25 Aug 1999 16:16:25 +0000 [thread overview]
Message-ID: <marc-linux-sound-93559778407435@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93559158330469@msgid-missing>
On Wed, 25 Aug 1999, Andrea Arcangeli wrote:
> On Wed, 25 Aug 1999, Benno Senoner wrote:
>
> >will mlock() automatically cause all pages to be read from the file ?
>
> Yes.
>
> >But since I already do an mlockall() at the beginnig, there is no need of
> >additional mlock()s
>
> Yes (if you use MCL_FUTURE).
>
> Andrea
Yes, I run with mlockall(MCL_CURRENT|MCL_FUTURE)
I can confirm this now:
I just removed my memcpy()s for testing purposes, and the app loads the
data nicely.
Pratically this means that if you enabled MCL_FUTURE,
mmap() will return only after all the mapped segment of the file resides in
memory.
Correct me please if I am wrong.
regards,
Benno.
next prev parent reply other threads:[~1999-08-25 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-25 14:21 mmap() better than read() fro streaming, Was: Re: Streaming disk I/O kills file buffering and ma Alan Cox
1999-08-25 14:33 ` mmap() better than read() fro streaming, Was: Re: Streaming disk I/O kills file buffering and makes Benno Senoner
1999-08-25 15:02 ` mmap() better than read() fro streaming, Was: Re: Streaming disk I/O kills file buffering and ma Benno Senoner
1999-08-25 15:39 ` mmap() better than read() fro streaming, Was: Re: Streaming disk Andrea Arcangeli
1999-08-25 16:16 ` Benno Senoner [this message]
1999-08-26 16:55 ` mmap() better than read() fro streaming, Was: Re: Streaming disk I/O kills file buffering and ma Stephen C. Tweedie
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=marc-linux-sound-93559778407435@msgid-missing \
--to=sbenno@gardena.net \
--cc=linux-sound@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