From: Oleg Drokin <green@namesys.com>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: high system usage with kmail in 2.5.7X
Date: Thu, 3 Jul 2003 16:49:47 +0400 [thread overview]
Message-ID: <20030703124947.GA819@namesys.com> (raw)
In-Reply-To: <200307031637.46227.rathamahata@php4.ru>
Hello!
On Thu, Jul 03, 2003 at 04:37:46PM +0400, Sergey S. Kostyliov wrote:
> I experienced an abnormally high system usage whith kmail
> (KDE mail client). This is usually happened when I click on a
> huge mail folder. Then kmail just stops responding for a dozens of seconds.
> Seems like problem started around 2.5.70 (2.5.69 doesn't compile on my box,
> 2.5.68 works fine for me).
This is a kmail 3.0x problem (with large recommended i/o sizes), it is reported that upgrading to kmail 3.1+ will help.
Alternatively you can mount your reiserfs volumes with "-o nolargeio=1"
Bye,
Oleg
next prev parent reply other threads:[~2003-07-03 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 12:37 high system usage with kmail in 2.5.7X Sergey S. Kostyliov
2003-07-03 12:49 ` Oleg Drokin [this message]
2003-07-03 14:02 ` Sergey S. Kostyliov
2003-07-03 14:11 ` Sergey S. Kostyliov
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=20030703124947.GA819@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@php4.ru \
/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