mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Alexander Gran <alex@zodiac.dnsalias.org>,
	"E.Gryaznova" <grev@namesys.com>
Cc: reiserfs-dev <reiserfs-dev@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: Fw: 2.6.11-rc5-mm1: reiser4 eating cpu time
Date: Tue, 15 Mar 2005 08:57:36 +0200	[thread overview]
Message-ID: <200503150857.37419.vda@ilport.com.ua> (raw)
In-Reply-To: <200503131424.33498@zodiac.zodiac.dnsalias.org>

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


  parent reply	other threads:[~2005-03-15  6:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050303184456.534aedb6.akpm@osdl.org>
     [not found] ` <4230582F.2050503@namesys.com>
2005-03-13 13:24   ` Alexander Gran
2005-03-13 13:44     ` Fredrik Tolf
2005-03-13 13:55       ` Alexander Gran
2005-03-15  6:57     ` Denis Vlasenko [this message]
2005-03-16 12:56       ` Alexander Gran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503150857.37419.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=alex@zodiac.dnsalias.org \
    --cc=grev@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®