linux-kernel - Re: high system cpu load during intense disk i/o

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 10 Aug 2007 09:06:03 +0200
From:	Rafał Bilski <rafalbilski@...eria.pl>
To:	Dimitrios Apostolou <jimis@....net>
Cc:	linux-kernel@...r.kernel.org, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: high system cpu load during intense disk i/o

> So I would assume that delay_tsc() probably only makes the situation worse for 
> the libata tests, but the real problem is at __switch_to() and schedule(). Do 
> you agree with these assumptions?
Yes. I agree that percentage of CPU time is unreasonably high for these 
functions. But not only for them.
> Is there a way to for oprofile to report the time spent in function calls 
> depending on the call trace?
I don't know any.
> Thanks again for the help. I guess if that doesn't lead anywhere I'll just 
> start compiling older vanilla kernels and see when the problem dissapears. 
> But this needs a lot of time and I'm not sure for how long I'll be able to 
> not offer any service with those disks (I was supposed to use RAID 0 to 
> provide storage space with them, but with the current problems that wouldn't 
> be so wise).
Probably this is the best and fastest way to diagnose problem.
> Dimitris
Regards
Rafał


----------------------------------------------------------------------
Taśm Renaty i Andrzeja tu nie znajdziesz.
Mamy coś lepszego ... 

>>>http://link.interia.pl/f1b41


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/