mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Gran <alex@zodiac.dnsalias.org>
To: "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: Sun, 13 Mar 2005 14:24:33 +0100	[thread overview]
Message-ID: <200503131424.33498@zodiac.zodiac.dnsalias.org> (raw)
In-Reply-To: <4230582F.2050503@namesys.com>

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. 
Please note that this happens when the file is in cache too. No Idea what 
kwrite is doing here, though.
In the case described earlier ent:hda6. was eating my cpu cyles, even after 
kwrite was killed!

regards
Alex

Am Donnerstag, 10. März 2005 15:22 schrieb E.Gryaznova:
> I opened  190Mb textfile with kwrite and tried  to  do  "goto line
> number 1 800 000" (file has about 6 000 000 lines). File is placed not
> on reiser4 but on ext2 partition. And I see that  kwrite eats about
> 90-100% CPU.
> Does kwrite work fine for you on so big files on ext2 filesystem?
>
> I have the following kde version:
> grev@flint:~> kwrite --version
> Qt: 3.2.1
> KDE: 3.1.4
> KWrite: 4.1
>
> Thanks,
> Lena.
>
> >Begin forwarded message:
> >
> >Date: Fri, 4 Mar 2005 02:24:36 +0100
> >From: Alexander Gran <alex@zodiac.dnsalias.org>
> >To: linux-kernel@vger.kernel.org
> >Subject: 2.6.11-rc5-mm1: reiser4 eating cpu time
> >
> >
> >Hi,
> >
> >I have a reiser4 partition on a local IDE disk. I opened a 130MB textfile
> > with kwrite, and killed it while ot opened the file (took to long...)
> > diskio was finished at this point.
> >a [ent:hda6.] Process was eating 100% CPU time for several (54) seconds.
> >Is this a normal, expected behaviour?
> >After trying again, pdflush was eating much cpu time, about the same (50+
> >secs) Note that this happend after reiser4 panic (on an external disk as
> >reported several minutes ago).
> >
> >regards
> >Alex

-- 
Encrypted Mails welcome.
PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291

       reply	other threads:[~2005-03-13 13:24 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 [this message]
2005-03-13 13:44     ` Fredrik Tolf
2005-03-13 13:55       ` Alexander Gran
2005-03-15  6:57     ` Denis Vlasenko
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=200503131424.33498@zodiac.zodiac.dnsalias.org \
    --to=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®