Skip to contentSkip to conversation

remove _STK_LIM_MAX override

DISCUSSION Helge Deller 2 participants 4 messages Apr 28, 2014 – May 1, 2014 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

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?

Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 10 lines · Helge Deller

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?

Thanks Helge, I'll look into that.

Presumably the parisc resource.h can be removed and added to generic-y now if _STK_LIM_MAX is removed?

Cheers
James
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAAG0J997TYcaqLFqfvHMwV+UoH5xTePSG+ZCz8sZPiTShi-8EQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#4 lore raw
Quoted 9 lines · James Hogan
Quoted 8 lines · Helge Deller

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/

Quoted 7 lines
Quoted 2 lines

It seems metag is now the only arch left which overrides _STK_LIM_MAX. Maybe you need to revisit that too?

Thanks Helge, I'll look into that.

Presumably the parisc resource.h can be removed and added to generic-y now if _STK_LIM_MAX is removed?

Yes, I will change that too.

Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#5 lore raw
In reply to a message not in the archive
Quoted 10 lines · Helge Deller

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