fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
orivej has joined #systemtap
orivej has quit [Ping timeout: 265 seconds]
khaled has joined #systemtap
orivej has joined #systemtap
_whitelogger has joined #systemtap
KDr2 has joined #systemtap
KDr2 has quit [Quit: Connection closed for inactivity]
Guest65867 has quit [Ping timeout: 246 seconds]
Guest65867 has joined #systemtap
higgins` has joined #systemtap
higgins has quit [Ping timeout: 268 seconds]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #systemtap
orivej has quit [Ping timeout: 240 seconds]
khaled has quit [Quit: Konversation terminated!]
Guest65867 has quit [Ping timeout: 240 seconds]
Guest65867 has joined #systemtap
gromero_ has quit [Ping timeout: 240 seconds]
gromero_ has joined #systemtap
<agentzh_>
hi folks, is there any plan to make stap's kernel module compilation parallelable?
<agentzh_>
it seems that the most of the time is spent on a single gigantic xxx_src.c file which cannot utilize multiple cpu cores.
<agentzh_>
i guess it'll make stap run much faster since i'm seeing pass 4 is dominating the tool preparation time.
<agentzh_>
like this: "Pass 4: compiled C into "foo.ko" in 2980usr/460sys/3126real ms."
<agentzh_>
or much worse: "Pass 4: compiled C into "c_off_fgraph.ko" in 9950usr/870sys/9271real ms."