public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rajis at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28310] Do not use affinity mask for sysconf (_SC_NPROCESSORS_CONF) Date: Fri, 03 Nov 2023 12:37:14 +0000 [thread overview] Message-ID: <bug-28310-131-Aicnksgz6r@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28310-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28310 Rajalakshmi <rajis at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rajis at linux dot ibm.com --- Comment #2 from Rajalakshmi <rajis at linux dot ibm.com> --- Hi Adhemerval Commit 342298278eabc75baabcaced110a11a02c3d3580 reverted the use of sched_getaffinity on get_nprocs() However, in commit 11a02b035b464ab6813676adfd19c4a59c36d907 we still use __get_nprocs_sched () instead of __get_nprocs() in malloc/arena.c There is a performance degradation issue reported on POWER10 RHEL9(glibc 2.34) compared to RHEL 8 *(glibc 2.28) when using IBM ESSL application with 80 omp threads. While debugging , figured out that using __get_nprocs() instead of __get_nprocs_sched () in malloc/arena.c fixes the issue. I don’t have reduced test to replicate the issue. Do you have any comments/suggestions? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-03 12:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-06 10:46 [Bug libc/28310] New: " fweimer at redhat dot com 2021-09-06 13:28 ` [Bug libc/28310] " nsaenzju at redhat dot com 2021-09-06 18:04 ` adhemerval.zanella at linaro dot org 2021-09-27 12:33 ` adhemerval.zanella at linaro dot org 2023-11-03 12:37 ` rajis at linux dot ibm.com [this message] 2023-11-06 13:35 ` adhemerval.zanella at linaro dot org
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=bug-28310-131-Aicnksgz6r@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).