public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "extproxy at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/11159] New: lock contention within regexec() when used from multiple threads Date: Mon, 11 Jan 2010 09:40:00 -0000 [thread overview] Message-ID: <20100111094018.11159.extproxy@gmail.com> (raw) I have a program that uses multiple threads. Each thread makes heavy use of regular expression matches by calling the glibc regexec() function. Unfortunately, this function seems to acquire a global lock - which causes poor performance in a multi-threaded environment. I'm not even sure what regexec() needs to lock - it really doesn't need access to any global state. Maybe it accesses some global locale object or something. Anyways, it doesn't need to acquire a write lock - a read lock should have sufficed. Alternatively, a thread-local data structure could be considered. Hope future releases of glibc can address this performance bug. -- Summary: lock contention within regexec() when used from multiple threads Product: glibc Version: 2.10 Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: drepper at redhat dot com ReportedBy: extproxy at gmail dot com CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11159 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-01-11 9:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-11 9:40 extproxy at gmail dot com [this message] 2010-01-11 9:58 ` [Bug regex/11159] " schwab at linux-m68k dot org 2010-01-11 17:46 ` extproxy at gmail dot com 2010-01-11 17:55 ` bonzini at gnu dot org 2010-01-11 18:01 ` extproxy at gmail dot com 2010-01-11 18:03 ` bonzini at gnu dot org 2010-01-15 7:51 ` drepper at redhat dot com
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=20100111094018.11159.extproxy@gmail.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@sources.redhat.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: 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).