public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15533] New: LD_AUDIT introduces an avoidable performance degradation Date: Fri, 24 May 2013 23:56:00 -0000 [thread overview] Message-ID: <bug-15533-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15533 Bug ID: 15533 Summary: LD_AUDIT introduces an avoidable performance degradation Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: amonakov at gmail dot com Created attachment 7044 --> http://sourceware.org/bugzilla/attachment.cgi?id=7044&action=edit testcase Introducing an audit library currently force-enables instrumenting for profiling in the dynamic linker (as if LD_AUDIT implied LD_PROFILE). However, this is not necessary if the audit library does not provide la_plt{enter,exit} symbols. Attached testcase demonstrates the performance hit: $ make test time ./main 0.47user 0.00system 0:00.48elapsed 99%CPU (0avgtext+0avgdata 1984maxresident)k 0inputs+0outputs (0major+170minor)pagefaults 0swaps time env LD_AUDIT=./libaudit.so ./main 8.96user 0.00system 0:08.97elapsed 99%CPU (0avgtext+0avgdata 3264maxresident)k 0inputs+0outputs (0major+442minor)pagefaults 0swaps -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-05-24 23:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-24 23:56 amonakov at gmail dot com [this message] 2013-05-25 0:27 ` [Bug dynamic-link/15533] " amonakov at gmail dot com 2014-06-13 17:36 ` fweimer at redhat dot com 2021-10-05 20:11 ` nnye at whitebeamsec dot com 2021-12-28 11:51 ` 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-15533-131@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).