Am Dienstag, 15. März 2005 07:57 schrieb Denis Vlasenko:
> Use strace -tt to find out whether kwrite spends that much CPU
> by doing zillions of syscalls or not.
Actually pdflush always kicks in after a write call. Summary:
% time seconds usecs/call callserrors syscall
--
On Sunday 13 March 2005 15:24, Alexander Gran wrote:
> Hi,
>
> Well, of course it cannot handle that large files (I wouldn't expect that,
> either). My Problem is that when I open the file, it's not just kwrite but
> other processes that need so much cpu time. That kwrite is eating cpu is ok.
Am Sonntag, 13. MÃrz 2005 14:44 schrieben Sie:
> That seems very much like expected behavior to me. I would expect kwrite
> to start loading the file, and then having pdflush kick in to page out
> parts of kwrite, so that it can allocate more memory. Then kwrite will
> continue to load until more o
On Sun, 2005-03-13 at 14:24 +0100, Alexander Gran wrote:
> Hi,
>
> Well, of course it cannot handle that large files (I wouldn't expect that,
> either). My Problem is that when I open the file, it's not just kwrite but
> other processes that need so much cpu time. That kwrite is eating cpu is o
Hi,
Well, of course it cannot handle that large files (I wouldn't expect that,
either). My Problem is that when I open the file, it's not just kwrite but
other processes that need so much cpu time. That kwrite is eating cpu is ok.
I cannot reproduce the behaviour for some reason however.
So f
5 matches
Mail list logo
