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. > I cannot reproduce the behaviour for some reason however. > So for short what's now (2.6.11-mm3) hapening: > I open a file of 150MB with kwrite. Kwrite start using all cpu it can get > After some seconds pdflush kicks in. Kwrite seems to wait, and pdflush is > eating cpu cyles. These 2 alternate for some time, until file is loaded.
I bet kwrite does something silly. Use strace -tt to find out whether kwrite spends that much CPU by doing zillions of syscalls or not. -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
