From: est@hyperreal.org
To: linux-sound@vger.kernel.org
Subject: Re: mmap()/mlockall()/read()
Date: Wed, 27 Oct 1999 21:15:21 +0000 [thread overview]
Message-ID: <marc-linux-sound-94105904620235@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94095888330340@msgid-missing>
Benno Senoner discourseth:
>
> I think the best fallback solution is the following (but not 100% reliable
> in the case of syscalls):
> mlock(MCL_CURRENT);
> mlock() malloec()ed aread
Hmm, I remain sceptical that I'll see large apps using this. Using
other-people's-libraries is common after all. It would mean a lot of
work that doesn't seem worth the benefit to me. However, it would be
pleasant if people proved me wrong. :)
> but strange,
> MAP_UNLOCKED seems to not exist on my 2.2.12 kernel !!
It doesn't exist..I made it up! :)
I think it would be A Good Idea, and it looks easy to add.
> > Eric is hard to satisfy. :)
>
> You are not the only !
> :-)
Thence comes progress.
Eric
prev parent reply other threads:[~1999-10-27 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 17:10 mmap()/mlockall()/read() est
1999-10-27 18:03 ` mmap()/mlockall()/read() Benno Senoner
1999-10-27 21:15 ` est [this message]
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-94105904620235@msgid-missing \
--to=est@hyperreal.org \
--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