public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhatch at ilm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15310] _dl_sort_fini is O(n^3) causing slow exit when many dsos Date: Thu, 28 Mar 2013 10:00:00 -0000 [thread overview] Message-ID: <bug-15310-131-jp4vSnJSxU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15310-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15310 --- Comment #11 from Don Hatch <dhatch at ilm dot com> 2013-03-28 10:00:12 UTC --- Created attachment 6955 --> http://sourceware.org/bugzilla/attachment.cgi?id=6955 Proposed initial patch, rearranging init/fini sorting in prep for overhaul. diffs from master at 7a86be6 Here's the proposed initial patch. Commit message would be something like: ========================================================================== Refactor ld.so init/fini sorting code in preparation for overhaul. - Init sorting code was in two places: dl-open.c and dl-deps.c; it was identical in both places except for the starting index which was i0=0 in dl-open.c and i0=1 in dl-deps.c. Moved this common code out into a new function _dl_sort_init that takes i0 as a parameter. - Moved _dl_sort_init and _dl_sort_fini out into two new files dl-sort-init.c and dl-sort-fini.c. This allows easy diffing between the two (which can be interesting) and may also help facilitate future efforts to unit test these two functions. No functional change here. ========================================================================== I don't have the copyright agreement in place yet, but it seems to me that I'm not introducing any copyrightable material in this initial patch-- I'm just moving existing code around. (okay I did add a comment at the top of each function). Let me know if I'm doing this right... -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-28 10:00 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-27 7:47 [Bug dynamic-link/15310] New: " dhatch at ilm dot com 2013-03-27 8:12 ` [Bug dynamic-link/15310] " dhatch at ilm dot com 2013-03-27 8:45 ` dhatch at ilm dot com 2013-03-27 12:57 ` carlos at redhat dot com 2013-03-27 14:19 ` ppluzhnikov at google dot com 2013-03-27 20:33 ` dhatch at ilm dot com 2013-03-27 20:50 ` [Bug dynamic-link/15310] New: " Ondřej Bílka 2013-03-27 20:50 ` [Bug dynamic-link/15310] " neleai at seznam dot cz 2013-03-27 21:00 ` carlos at redhat dot com 2013-03-27 21:07 ` carlos at redhat dot com 2013-03-27 21:13 ` law at redhat dot com 2013-03-27 23:44 ` dhatch at ilm dot com 2013-03-28 0:31 ` dhatch at ilm dot com 2013-03-28 7:42 ` Ondřej Bílka 2013-03-28 7:42 ` neleai at seznam dot cz 2013-03-28 10:00 ` dhatch at ilm dot com [this message] 2013-03-28 10:19 ` dhatch at ilm dot com 2013-03-28 17:09 ` law at redhat dot com 2013-03-28 17:31 ` dhatch at ilm dot com 2013-04-02 9:54 ` dhatch at ilm dot com 2013-04-02 11:31 ` Ondřej Bílka 2013-04-02 11:31 ` neleai at seznam dot cz 2013-04-02 13:07 ` dhatch at ilm dot com 2013-04-02 23:37 ` dhatch at ilm dot com 2013-04-03 7:57 ` Ondřej Bílka 2013-04-03 7:57 ` neleai at seznam dot cz 2013-04-06 21:07 ` carlos at redhat dot com 2014-06-13 13:51 ` fweimer at redhat dot com 2014-06-13 18:37 ` fweimer at redhat dot com 2021-10-27 14:58 ` adhemerval.zanella at linaro dot org 2021-10-27 14:59 ` 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-15310-131-jp4vSnJSxU@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).