From: "David Schwartz" <davids@webmaster.com>
To: "Mike Black" <mblack@csi-inc.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Problem with mlockall() and Threads: memory usage
Date: Tue, 18 May 2004 13:38:23 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKEEIJMBAA.davids@webmaster.com> (raw)
In-Reply-To: <40AA06ED.50203@beam.ltd.uk>
> Thanks for that.
> I have done some more investigating, and on my system (Standard RedHat 9)
> the stack ulimit is set to 8192 KBytes. So it appears that the thread
> library/kernel threads pre-allocates, and writes to, 8129 KBytes
> of stack per
> thread and so then mlockall() locks all of this in memory.
>
> Should'nt the Thread library grow the stack rather than
> preallocate it all even
> with mlockall() like malloc ?
I thought you wanted improved latency. Surely having to find a page for you
when your stack grows will add unpredictable latency. So, no, the thread
library should reserve the stack when 'mlockall(MCL_FUTURE)' is specified.
I do agree that having an 'initial stack size' in additional to a 'maximum
stack size' would be a good idea. The former good for application that are
concerned about physical memory usage and the latter for applications
concerned about virtual memory usage.
DS
next prev parent reply other threads:[~2004-05-18 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:10 Terry Barnaby
[not found] ` <041501c43cc9$28aaed00$c8de11cc@black>
2004-05-18 12:51 ` Terry Barnaby
2004-05-18 20:38 ` David Schwartz [this message]
2004-05-19 8:45 ` Terry Barnaby
2004-05-20 0:23 ` Elladan
2004-05-21 14:28 ` Terry Barnaby
2004-05-21 14:28 ` Terry Barnaby
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=MDEHLPKNGKAHNMBLJOLKEEIJMBAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csi-inc.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®