From: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
To: Helge Deller <deller-Mmb7MZpHnFY@public.gmane.org>,
linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: John David Anglin <dave.anglin-CzeTG9NwML0@public.gmane.org>
Subject: Re: remove _STK_LIM_MAX override
Date: Thu, 1 May 2014 12:22:32 +0100 [thread overview]
Message-ID: <53622E78.9020703@imgtec.com> (raw)
In-Reply-To: <535EAA4E.800-Mmb7MZpHnFY@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On 28/04/14 20:21, Helge Deller wrote:
> Dear metag people,
>
> on the parisc arch we found a problem with GNU make, that our process stacks became too big so that many debian packages didn't built because not enough threads (started via GNU make) could be created.
>
> The final solution was to remove our arch-specifc _STK_LIM_MAX override.
> I will push this patch for parisc upstream soon:
> https://patchwork.kernel.org/patch/4072991/
>
> It seems metag is now the only arch left which overrides _STK_LIM_MAX.
> Maybe you need to revisit that too?
Hi Helge,
Could you clarify the exact problem? As far as I can tell from strace
experimentation GNU make will reset the RLIMIT_STACK soft limit to it's
previous value prior to forking off any children, and doesn't appear to
make use of pthreads itself either.
That's not to say the default hard limit override shouldn't be removed.
I think it was only there to prevent the excessively large 1GB default
stack size being used and causing problems with Meta's limited virtual
address space (which is effectively fixed by your other patch).
Thanks
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-05-01 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 19:21 remove _STK_LIM_MAX override Helge Deller
[not found] ` <535EAA4E.800-Mmb7MZpHnFY@public.gmane.org>
2014-04-28 23:11 ` James Hogan
[not found] ` <CAAG0J997TYcaqLFqfvHMwV+UoH5xTePSG+ZCz8sZPiTShi-8EQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-29 7:01 ` Helge Deller
2014-05-01 11:22 ` James Hogan [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=53622E78.9020703@imgtec.com \
--to=james.hogan-1axoqhu6uovqt0dzr+alfa@public.gmane.org \
--cc=dave.anglin-CzeTG9NwML0@public.gmane.org \
--cc=deller-Mmb7MZpHnFY@public.gmane.org \
--cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.