From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14063 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Raphael Cohn Newsgroups: gmane.linux.lib.musl.general Subject: Thread-local memory for thread structures Date: Thu, 11 Apr 2019 12:12:46 +0100 Message-ID: Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="158669"; mail-complaints-to="usenet@blaine.gmane.org" To: musl@lists.openwall.com Original-X-From: musl-return-14079-gllmg-musl=m.gmane.org@lists.openwall.com Thu Apr 11 13:13:14 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hEXdp-000fAI-CR for gllmg-musl@m.gmane.org; Thu, 11 Apr 2019 13:13:13 +0200 Original-Received: (qmail 8185 invoked by uid 550); 11 Apr 2019 11:13:09 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 8154 invoked from network); 11 Apr 2019 11:13:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stormmq-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=xKqRjUjqMYQr9qmbBKj3v/Wq2FOVfWSWEHbbrTpQTRI=; b=jnSKr307PB4hx8G8UTMCAeQsz1DR4wsSO5x1F/QzMrvmyneio5tJ/DNe2JBE68COcs 78GsB9njF/vDNddZZ+oDXWk+yhcOC1hgz4mCN2IZeJXW3QtKS0/DDtUyCPde5rynImUs 8N6VMl+Q56AmAps5sCQf1oCdwM7i6+3nAraEYRYyE4YdEUP2x8C2xFQ3pqqkugIh2XOs Y/sLmYXhPCN/7txi+nPZyr4+p/A/+H1tAKX5ruHi+QatfwIcAzCB36gbswBqKhWYeb5r jDCpjZ/fnNPbJRXEeTnLnYZRQNA9/sxRxgwkzfOuRi6/HuGudaz/zP1pbhupXRVdk4J5 UZ5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xKqRjUjqMYQr9qmbBKj3v/Wq2FOVfWSWEHbbrTpQTRI=; b=XFgFs1Pr0cZfm+NhCmSu57+37bE4YsNno+bCJIlNJTdIumH8M6tOvxJihWcPu8Gz1i 3ynCEHz5w20aap2hfvlfMPx1ZEMIrJrlx7a65uj/2AVN74XNAR+O7ZpWrlkRP9HxgGQv n5Andv1heZLBe++ei0E3AJ8Jhoz9yIjYQufjKrYq+yXGhJZrpKTyqxMZemnUbGZFQ/Av klUuxKdFJckIRe0dLml4M+iUQ8EzRD2V49YKd11tOy1E83AJFU94Lz09BhzGm1AxwA3s yMRW0UAAAa5MCG2hVDpf4oTsRcgrY4KRP5pqpo37ETF4+a1OJy7Xp5dtXSnrusgmtroS f1+g== X-Gm-Message-State: APjAAAVk1jO2+67FduBonXld1/s9aceywWrjuFEfygzoV4g60JB18xkw GJcfvEbx+/USETODkhwR3laMqWW3Epxw5HY91phhmlyvanV7SA== X-Google-Smtp-Source: APXvYqz202w1YIxUvk7zJfw+5ByuZv6CURE+qEoWXDpkz1LbUBLJuz4ODefusP9/LnPbUzJHaokdywKtMmxUFcNpd5s= X-Received: by 2002:a17:906:6050:: with SMTP id p16mr26669143ejj.173.1554981177169; Thu, 11 Apr 2019 04:12:57 -0700 (PDT) Xref: news.gmane.org gmane.linux.lib.musl.general:14063 Archived-At: Dear List, I'm playing around with allocating 100s of bytes of TLS memory for various purposes. Something I noticed in the code for creating the mmap'd memory for TLS is that it does not (quite reasonably) assign it a NUMA memory policy. I'd like to assign a NUMA memory policy to the memory used for managing a thread. Is there anything 'underhanded' I can do to find out its location and size? I realize anything is likely to be brittle. Ideally what I'd like is a 'set NUMA memory policy of this thead's mmap'd management memory to the local NUMA node [once I've scheduled it to run a particular set of CPUs]. Any suggestions? Raph