From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Kyle Moffett <mrmacman_g4@mac.com>
Subject: Re: mmap error?
Date: Mon, 02 Apr 2007 15:35:17 -0400 [thread overview]
Message-ID: <200704021535.17567.gene.heskett@gmail.com> (raw)
In-Reply-To: <8EF5AE61-FC1C-4BA2-BB8D-B55221D8846B@mac.com>
On Monday 02 April 2007, Kyle Moffett wrote:
>On Apr 02, 2007, at 13:54:28, Gene Heskett wrote:
>> Ahh, thank you very much. But I have 7.0, supposedly fixed,
>> sigh... That did fix it, the dvd is burning as I type, again thanks.
>>
>> ???? Can I put this into rc.local so its global? I guess I will
>> just for effects. Or is there an option in a make xconfig to reset
>> this to a usable sized limit?, because I can see cups also having
>> problems since I have its render cache set for 127 megs, which
>> should also trigger this.
>
>Well, that's not a limit on how much memory you can map, it's a limit
>on how many pages you can lock into memory (as in, cannot be swapped
>out or written back to disk and reused). For low-latency
>applications (IE: cd burning) you need to have all memory mlocked so
>that you don't get a low-latency wakup and then promptly lose all
>latency guarantees by swapping madly, but something like CUPS doesn't
>have a problem because it doesn't use mlock() or mlockall().
>
Ah, that clarifies that then, thanks Kyle.
>Cheers,
>Kyle Moffett
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The perversity of nature is nowhere better demonstrated by the fact that,
when
exposed to the same atmosphere, bread becomes hard while crackers become
soft.
prev parent reply other threads:[~2007-04-02 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:30 Gene Heskett
2007-04-02 17:35 ` Ken Moffat
2007-04-02 17:54 ` Gene Heskett
2007-04-02 18:02 ` Kyle Moffett
2007-04-02 19:35 ` Gene Heskett [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=200704021535.17567.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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®