From: Andrew Morton <akpm@digeo.com>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.69-mm2] Very slow read syscall
Date: Wed, 7 May 2003 16:00:49 -0700 [thread overview]
Message-ID: <20030507160049.4352009b.akpm@digeo.com> (raw)
In-Reply-To: <200305080055.23653.schlicht@uni-mannheim.de>
Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>
> Hi,
>
> I've noticed that the read syscall is very slow with 2.5.69-mm2 compared to
> 2.5.69-bk2. I especially could 'feel' it while using kmail. When kmail is
> closed and it compresses its Mail folder I could measure it.
>
> The straces and oprofiles for this action are attached for the two kernel
> versions mentioned above.
>
> As you can see the time for closing kmail increased from about 2 seconds to
> about 155 seconds. A read system call needs 931usecs instead of 12usecs...
> The profile shows that the most time is spent in __copy_to_user_ll.
> As CONFIG_X86_WP_WORKS_OK is defined in my config this function should be the
> same in -mm2 and -bk2, so it seems it simply is called more often...
>
> I am using the anticipatory scheduling elevator, but it 'feels' the same with
> CFQ or DL. But I can mesure it if you want...
This is due to a bug in kmail, and the reiserfs_file_write patch.
One thing which that patch does is to increase the stat.st_blksize hint
which reiserfs provides to applications. By a lot - from 4k to 128k I
think.
Problem is, some KDE apps see that hint and then promptly balls it up.
They read 128k at offset 0, then 128k at offset 4k, then 128k at offset 8k,
etc.
Apparently, upgrading kmail will fix it.
parent reply other threads:[~2003-05-07 22:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200305080055.23653.schlicht@uni-mannheim.de>]
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=20030507160049.4352009b.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@uni-mannheim.de \
/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®