Re: [PATCH] LatencyTop: make reason (blk_execute_rq+0x7a/0xd) known

Arjan van de Ven wrote: > Török Edwin wrote: >> >> Cause Maximum >> Average >> SCSI device ioctl 34.2 msec >> 14.4 msec > > great! I'll put this into my patchkit! Thanks. >> I also noticed some unsigned

Re: [PATCH] LatencyTop: make reason (blk_execute_rq+0x7a/0xd) known

Arjan van de Ven <[EMAIL PROTECTED]> writes: > Török Edwin wrote: >> [...] >> P.S.: LatencyTop could have a feature to ask for more details on unknown >> latency reasons, and it would generate a systemtap script itself, that >> would show the backtraces to help figure out whats going on. > > I've

Re: [PATCH] LatencyTop: make reason (blk_execute_rq+0x7a/0xd) known

Török Edwin wrote: Hi Arjan, One of the top reasons in latencytop is Unknown reason (blk_execute_rq+0x7a/0xd) 152.3 msec 49.0 msec Its from hddtemp, hald-addon-storage, ... I wrote a simple systemtap script [1] to find out where its called from, and its definitely from the io

[PATCH] LatencyTop: make reason (blk_execute_rq+0x7a/0xd) known

Hi Arjan, One of the top reasons in latencytop is Unknown reason (blk_execute_rq+0x7a/0xd) 152.3 msec 49.0 msec Its from hddtemp, hald-addon-storage, ... I wrote a simple systemtap script [1] to find out where its called from, and its definitely from the ioctl (see below). 1820