From: Hugh Dickins <hugh@veritas.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch][rfc] mm: have expand_stack honour VM_LOCKED
Date: Fri, 17 Oct 2008 16:06:26 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810171545001.11791@blonde.site> (raw)
In-Reply-To: <20081017135528.GA6694@wotan.suse.de>
On Fri, 17 Oct 2008, Nick Piggin wrote:
>
> How do critical apps reserve and lock a required amount of stack? I
> thought there might be cases where failing to lock pages could cause
> problems there.
I'd have thought that an app that was desperate to avoid even minor
faults would be mlocking all the stack it might ever need later on:
not extending its stack with (one or more) minor faults but relying
on those to prevent minor faults on the gaps.
Ah, you think it might mlock the stack it already has, then touch a
lower address, and expect that to fault in the intervening pages:
well, I suppose it might expect that, but we've never done it,
so we'd have been causing it unnoticed problems for many years.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-10-17 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 5:01 Nick Piggin
2008-10-17 5:41 ` KOSAKI Motohiro
2008-10-17 9:08 ` Nick Piggin
2008-10-17 9:32 ` KOSAKI Motohiro
2008-10-17 9:33 ` KOSAKI Motohiro
2008-10-17 9:37 ` Nick Piggin
2008-10-17 12:50 ` Lee Schermerhorn
2008-10-17 12:48 ` Lee Schermerhorn
2008-10-17 13:42 ` Hugh Dickins
2008-10-17 13:55 ` Nick Piggin
2008-10-17 15:06 ` Hugh Dickins [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=Pine.LNX.4.64.0810171545001.11791@blonde.site \
--to=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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