All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrea Arcangeli <andrea@suse.de>,
	Andrew Morton <akpm@zip.com.au>,
	linux-kernel@vger.kernel.org,
	Manfred Spraul <manfreds@colorfullife.com>
Subject: Re: Q: behaviour of mlockall(MCL_FUTURE) and VM_GROWSDOWN segments
Date: Sat, 12 Jan 2002 17:07:42 +0100	[thread overview]
Message-ID: <3C405F4E.EADB2294@colorfullife.com> (raw)
In-Reply-To: <3C3F3C7F.76CCAF76@colorfullife.com.suse.lists.linux.kernel> <3C3F4FC6.97A6A66D@zip.com.au.suse.lists.linux.kernel> <p73r8ow4dd7.fsf@oldwotan.suse.de> <20020112163332.M1482@inspiron.school.suse.de> <20020112165443.A13179@wotan.suse.de>

Andi Kleen wrote:
> 
> For the stack they can get minor faults anyways when they allocate new
> stack space below ESP. There is no good way to fix that from the kernel; the
> application has to preallocate its memory on stack. I think it's reasonable
> if it does the same for holes on the stack.
>
Ok, everyone agrees that mlockall() should not grow VM_GROWSDOWN
segments to their maximum size.
Should the page fault handler fill the hole created by

void * grow_stack(void)
{
	char data[100000];
	data[0] = '0';
	return data;
}

The principle of least surprise would mean filling holes, but OTHO sane
apps would use memset(data,0,sizeof(data)).

--
	Manfred

  reply	other threads:[~2002-01-12 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C3F3C7F.76CCAF76@colorfullife.com.suse.lists.linux.kernel>
     [not found] ` <3C3F4FC6.97A6A66D@zip.com.au.suse.lists.linux.kernel>
2002-01-12  0:33   ` Q: behaviour of mlockall(MCL_FUTURE) and VM_GROWSDOWN segments Andi Kleen
2002-01-12  1:04     ` Andrew Morton
2002-01-12 15:33     ` Andrea Arcangeli
2002-01-12 15:54       ` Andi Kleen
2002-01-12 16:07         ` Manfred Spraul [this message]
2002-01-12 16:17           ` Andrea Arcangeli
2002-01-12 16:14         ` Andrea Arcangeli
2002-01-11 19:26 Manfred Spraul
2002-01-11 20:49 ` Andrew Morton
2002-01-11 23:45   ` Richard Gooch

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=3C405F4E.EADB2294@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=ak@suse.de \
    --cc=akpm@zip.com.au \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfreds@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.