Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 69517 Details for
Bug 107635
sys-fs/convertfs eats 100% CPU for days on end
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
devremap profiling output
devremap-gprof.txt (text/plain), 13.72 KB, created by
Andreas Klauer
on 2005-09-29 12:17:30 UTC
(
hide
)
Description:
devremap profiling output
Filename:
MIME Type:
Creator:
Andreas Klauer
Created:
2005-09-29 12:17:30 UTC
Size:
13.72 KB
patch
obsolete
>Flat profile: > >Each sample counts as 0.01 seconds. > % cumulative self self total > time seconds seconds calls s/call s/call name > 99.85 459.99 459.99 6120 0.08 0.08 find_cross_block > 0.09 460.40 0.41 12246 0.00 0.00 log_bfix > 0.05 460.62 0.22 15166 0.00 0.00 init_physmap > 0.02 460.73 0.11 6 0.02 76.77 prepare_log > 0.02 460.80 0.07 2128 0.00 0.00 balloc > 0.01 460.83 0.03 6120 0.00 0.00 log_bmove0 > 0.00 460.85 0.02 6120 0.00 0.00 handle_cross_block > 0.00 460.86 0.01 12252 0.00 0.00 next_bmove > 0.00 460.87 0.01 6 0.00 0.00 commit_log_stage1 > 0.00 460.87 0.00 14308 0.00 0.00 bmove > 0.00 460.87 0.00 6126 0.00 0.00 log_bmove1 > 0.00 460.87 0.00 2062 0.00 0.00 log_bmove2 > 0.00 460.87 0.00 24 0.00 0.00 commit > 0.00 460.87 0.00 24 0.00 0.00 write_log_part > 0.00 460.87 0.00 12 0.00 0.00 first_bmove > 0.00 460.87 0.00 6 0.00 0.00 commit_log > 0.00 460.87 0.00 6 0.00 0.00 commit_log_stage2 > 0.00 460.87 0.00 6 0.00 0.00 commit_log_stage3 > 0.00 460.87 0.00 6 0.00 0.00 init_reserved > 0.00 460.87 0.00 6 0.00 0.00 write_log > 0.00 460.87 0.00 1 0.00 0.00 init_log > 0.00 460.87 0.00 1 0.00 0.22 load_index > 0.00 460.87 0.00 1 0.00 0.00 load_superblock > 0.00 460.87 0.00 1 0.00 0.00 replay_log > > % the percentage of the total running time of the >time program used by this function. > >cumulative a running sum of the number of seconds accounted > seconds for by this function and those listed above it. > > self the number of seconds accounted for by this >seconds function alone. This is the major sort for this > listing. > >calls the number of times this function was invoked, if > this function is profiled, else blank. > > self the average number of milliseconds spent in this >ms/call function per call, if this function is profiled, > else blank. > > total the average number of milliseconds spent in this >ms/call function and its descendents per call, if this > function is profiled, else blank. > >name the name of the function. This is the minor sort > for this listing. The index shows the location of > the function in the gprof listing. If the index is > in parenthesis it shows where it would appear in > the gprof listing if it were to be printed. > > Call graph (explanation follows) > > >granularity: each sample hit covers 2 byte(s) for 0.00% of 460.87 seconds > >index % time self children called name > <spontaneous> >[1] 100.0 0.00 460.87 main [1] > 0.11 460.52 6/6 prepare_log [2] > 0.00 0.22 1/1 load_index [7] > 0.00 0.01 6/6 commit_log [11] > 0.00 0.00 6/6 write_log [14] > 0.00 0.00 1/1 init_log [23] > 0.00 0.00 1/1 load_superblock [24] > 0.00 0.00 1/1 replay_log [25] >----------------------------------------------- > 0.11 460.52 6/6 main [1] >[2] 99.9 0.11 460.52 6 prepare_log [2] > 459.99 0.32 6120/6120 find_cross_block [3] > 0.21 0.00 6126/12246 log_bfix [4] > 0.01 0.00 12252/12252 next_bmove [10] > 0.00 0.00 6126/6126 log_bmove1 [16] > 0.00 0.00 12/12 first_bmove [19] > 0.00 0.00 6/6 init_reserved [22] >----------------------------------------------- > 459.99 0.32 6120/6120 prepare_log [2] >[3] 99.9 459.99 0.32 6120 find_cross_block [3] > 0.02 0.30 6120/6120 handle_cross_block [5] >----------------------------------------------- > 0.20 0.00 6120/12246 handle_cross_block [5] > 0.21 0.00 6126/12246 prepare_log [2] >[4] 0.1 0.41 0.00 12246 log_bfix [4] >----------------------------------------------- > 0.02 0.30 6120/6120 find_cross_block [3] >[5] 0.1 0.02 0.30 6120 handle_cross_block [5] > 0.20 0.00 6120/12246 log_bfix [4] > 0.07 0.00 2062/2128 balloc [8] > 0.03 0.00 6120/6120 log_bmove0 [9] > 0.00 0.00 2062/2062 log_bmove2 [17] >----------------------------------------------- > 0.22 0.00 15166/15166 load_index [7] >[6] 0.0 0.22 0.00 15166 init_physmap [6] >----------------------------------------------- > 0.00 0.22 1/1 main [1] >[7] 0.0 0.00 0.22 1 load_index [7] > 0.22 0.00 15166/15166 init_physmap [6] >----------------------------------------------- > 0.00 0.00 66/2128 write_log_part [13] > 0.07 0.00 2062/2128 handle_cross_block [5] >[8] 0.0 0.07 0.00 2128 balloc [8] >----------------------------------------------- > 0.03 0.00 6120/6120 handle_cross_block [5] >[9] 0.0 0.03 0.00 6120 log_bmove0 [9] >----------------------------------------------- > 0.01 0.00 12252/12252 prepare_log [2] >[10] 0.0 0.01 0.00 12252 next_bmove [10] >----------------------------------------------- > 0.00 0.01 6/6 main [1] >[11] 0.0 0.00 0.01 6 commit_log [11] > 0.01 0.00 6/6 commit_log_stage1 [12] > 0.00 0.00 6/6 commit_log_stage2 [20] > 0.00 0.00 6/6 commit_log_stage3 [21] >----------------------------------------------- > 0.01 0.00 6/6 commit_log [11] >[12] 0.0 0.01 0.00 6 commit_log_stage1 [12] > 0.00 0.00 6120/14308 bmove [15] > 0.00 0.00 6/24 commit [18] >----------------------------------------------- > 0.00 0.00 24/24 write_log [14] >[13] 0.0 0.00 0.00 24 write_log_part [13] > 0.00 0.00 66/2128 balloc [8] >----------------------------------------------- > 0.00 0.00 6/6 main [1] >[14] 0.0 0.00 0.00 6 write_log [14] > 0.00 0.00 24/24 write_log_part [13] > 0.00 0.00 6/24 commit [18] >----------------------------------------------- > 0.00 0.00 2062/14308 commit_log_stage3 [21] > 0.00 0.00 6120/14308 commit_log_stage1 [12] > 0.00 0.00 6126/14308 commit_log_stage2 [20] >[15] 0.0 0.00 0.00 14308 bmove [15] >----------------------------------------------- > 0.00 0.00 6126/6126 prepare_log [2] >[16] 0.0 0.00 0.00 6126 log_bmove1 [16] >----------------------------------------------- > 0.00 0.00 2062/2062 handle_cross_block [5] >[17] 0.0 0.00 0.00 2062 log_bmove2 [17] >----------------------------------------------- > 0.00 0.00 6/24 write_log [14] > 0.00 0.00 6/24 commit_log_stage1 [12] > 0.00 0.00 6/24 commit_log_stage2 [20] > 0.00 0.00 6/24 commit_log_stage3 [21] >[18] 0.0 0.00 0.00 24 commit [18] >----------------------------------------------- > 0.00 0.00 12/12 prepare_log [2] >[19] 0.0 0.00 0.00 12 first_bmove [19] >----------------------------------------------- > 0.00 0.00 6/6 commit_log [11] >[20] 0.0 0.00 0.00 6 commit_log_stage2 [20] > 0.00 0.00 6126/14308 bmove [15] > 0.00 0.00 6/24 commit [18] >----------------------------------------------- > 0.00 0.00 6/6 commit_log [11] >[21] 0.0 0.00 0.00 6 commit_log_stage3 [21] > 0.00 0.00 2062/14308 bmove [15] > 0.00 0.00 6/24 commit [18] >----------------------------------------------- > 0.00 0.00 6/6 prepare_log [2] >[22] 0.0 0.00 0.00 6 init_reserved [22] >----------------------------------------------- > 0.00 0.00 1/1 main [1] >[23] 0.0 0.00 0.00 1 init_log [23] >----------------------------------------------- > 0.00 0.00 1/1 main [1] >[24] 0.0 0.00 0.00 1 load_superblock [24] >----------------------------------------------- > 0.00 0.00 1/1 main [1] >[25] 0.0 0.00 0.00 1 replay_log [25] >----------------------------------------------- > > This table describes the call tree of the program, and was sorted by > the total amount of time spent in each function and its children. > > Each entry in this table consists of several lines. The line with the > index number at the left hand margin lists the current function. > The lines above it list the functions that called this function, > and the lines below it list the functions this one called. > This line lists: > index A unique number given to each element of the table. > Index numbers are sorted numerically. > The index number is printed next to every function name so > it is easier to look up where the function in the table. > > % time This is the percentage of the `total' time that was spent > in this function and its children. Note that due to > different viewpoints, functions excluded by options, etc, > these numbers will NOT add up to 100%. > > self This is the total amount of time spent in this function. > > children This is the total amount of time propagated into this > function by its children. > > called This is the number of times the function was called. > If the function called itself recursively, the number > only includes non-recursive calls, and is followed by > a `+' and the number of recursive calls. > > name The name of the current function. The index number is > printed after it. If the function is a member of a > cycle, the cycle number is printed between the > function's name and the index number. > > > For the function's parents, the fields have the following meanings: > > self This is the amount of time that was propagated directly > from the function into this parent. > > children This is the amount of time that was propagated from > the function's children into this parent. > > called This is the number of times this parent called the > function `/' the total number of times the function > was called. Recursive calls to the function are not > included in the number after the `/'. > > name This is the name of the parent. The parent's index > number is printed after it. If the parent is a > member of a cycle, the cycle number is printed between > the name and the index number. > > If the parents of the function cannot be determined, the word > `<spontaneous>' is printed in the `name' field, and all the other > fields are blank. > > For the function's children, the fields have the following meanings: > > self This is the amount of time that was propagated directly > from the child into the function. > > children This is the amount of time that was propagated from the > child's children to the function. > > called This is the number of times the function called > this child `/' the total number of times the child > was called. Recursive calls by the child are not > listed in the number after the `/'. > > name This is the name of the child. The child's index > number is printed after it. If the child is a > member of a cycle, the cycle number is printed > between the name and the index number. > > If there are any cycles (circles) in the call graph, there is an > entry for the cycle-as-a-whole. This entry shows who called the > cycle (as parents) and the members of the cycle (as children.) > The `+' recursive calls entry shows the number of function calls that > were internal to the cycle, and the calls entry for each member shows, > for that member, how many times it was called from other members of > the cycle. > > >Index by function name > > [8] balloc (devremap.c) [19] first_bmove (devremap.c) [9] log_bmove0 (devremap.c) > [15] bmove (devremap.c) [5] handle_cross_block (devremap.c) [16] log_bmove1 (devremap.c) > [18] commit (devremap.c) [23] init_log (devremap.c) [17] log_bmove2 (devremap.c) > [11] commit_log (devremap.c) [6] init_physmap (devremap.c) [10] next_bmove (devremap.c) > [12] commit_log_stage1 (devremap.c) [22] init_reserved (devremap.c) [2] prepare_log (devremap.c) > [20] commit_log_stage2 (devremap.c) [7] load_index (devremap.c) [25] replay_log (devremap.c) > [21] commit_log_stage3 (devremap.c) [24] load_superblock (devremap.c) [14] write_log (devremap.c) > [3] find_cross_block (devremap.c) [4] log_bfix (devremap.c) [13] write_log_part (devremap.c)
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 107635
: 69517 |
69555