public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
	Carlos O'Donell <carlos@redhat.com>,
	Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	GNU C Library <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>, Jeff Law <law@redhat.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	Rich Felker <dalias@libc.org>,
	James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [RFC] nptl: change default stack guard size of threads
Date: Wed, 06 Dec 2017 13:13:00 -0000	[thread overview]
Message-ID: <4c1f71cd-ebe6-6fa7-a3c4-05b410e31ecd@redhat.com> (raw)
In-Reply-To: <DB6PR0801MB2053CF95BF1877527163A4EB83320@DB6PR0801MB2053.eurprd08.prod.outlook.com>

On 12/06/2017 02:10 PM, Wilco Dijkstra wrote:
> Florian Weimer wrote:
>> On 11/29/2017 11:38 PM, Carlos O'Donell wrote:
>>> On 11/29/2017 02:28 PM, Wilco Dijkstra wrote:
>>>> Why should it be any different from LP64? Typical page size will still be
>>>> 64KB, so a 4KB guard would be rounded up to 64KB. An ILP32 system
>>>> with 64KB pages could create  ~30000 threads per process. Does that
>>>> make it unusable?
>>>
>>> ... and this is already configurable via pthread_attr_setguardsize(), so
>>> you *could* tune a system to have smaller guards against the recommendation
>>> of the runtime authors?
>>
>> Sure, if you recompile your application.  That's not really a solution IMHO.
> 
> You've got to do that already in order to run it on ILP32 - there isn't exactly
> a large amount of existing ILP32 binaries around, let alone ones that need more
> than 30000 threads per process.

I wasn't talking about aarch64 ILP32, and I suspect neither was Carlos.

In my world, if you still have 32-bit binaries, it's because you lost 
the sources or the tools or knowledge to build them at some point.

Thanks,
Florian

  reply	other threads:[~2017-12-06 13:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 14:59 Szabolcs Nagy
2017-11-29 15:18 ` Florian Weimer
2017-11-29 18:17   ` Carlos O'Donell
2017-11-29 18:29     ` Rich Felker
2017-11-29 20:33       ` Florian Weimer
2017-11-29 18:40   ` Szabolcs Nagy
2017-11-29 20:44     ` Florian Weimer
2017-11-29 20:52       ` Rich Felker
2017-11-29 21:02         ` Florian Weimer
2017-11-29 23:13           ` Szabolcs Nagy
2017-12-05 10:55           ` James Greenhalgh
2017-12-06 12:51             ` Florian Weimer
2017-12-11 23:49             ` Jeff Law
2017-12-12 11:43               ` Szabolcs Nagy
2017-12-12 16:36                 ` Rich Felker
2017-12-12 18:07                   ` Szabolcs Nagy
2017-12-12 19:30               ` Florian Weimer
2017-12-13 11:58                 ` Szabolcs Nagy
2017-12-19 12:35             ` James Greenhalgh
2017-12-19 13:06               ` Florian Weimer
2017-12-19 18:21                 ` Szabolcs Nagy
2017-12-19 20:34                   ` Rich Felker
2017-12-20  4:42                     ` Jeff Law
2017-12-20  4:49                       ` Rich Felker
2017-12-27 13:08                         ` Wilco Dijkstra
2017-12-20  4:45                 ` Jeff Law
2017-11-29 22:28       ` Wilco Dijkstra
2017-11-29 22:38         ` Carlos O'Donell
2017-12-06 12:53           ` Florian Weimer
2017-12-06 13:10             ` Wilco Dijkstra
2017-12-06 13:13               ` Florian Weimer [this message]
2017-11-29 23:02         ` Rich Felker
2017-12-06 13:16         ` Florian Weimer
2017-12-06 13:40           ` Joseph Myers
2017-12-06 13:51             ` Florian Weimer
2017-12-06 14:44             ` Jeff Law
2017-12-06 14:27           ` Wilco Dijkstra
2017-12-06 20:41             ` Szabolcs Nagy
2017-12-06 21:24               ` Adhemerval Zanella
2017-12-06 22:08               ` Rich Felker
2017-12-08 18:28                 ` Szabolcs Nagy
2017-11-29 22:45       ` Szabolcs Nagy

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=4c1f71cd-ebe6-6fa7-a3c4-05b410e31ecd@redhat.com \
    --to=fweimer@redhat.com \
    --cc=James.Greenhalgh@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=carlos@redhat.com \
    --cc=dalias@libc.org \
    --cc=law@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).