From: Ingo Molnar <mingo@elte.hu>
To: poison <rc.poison@gmail.com>
Cc: Helmut Toplizer <bgrpt@toplitzer.net>, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.23 - acting funny
Date: Fri, 12 Oct 2007 08:05:16 +0200 [thread overview]
Message-ID: <20071012060516.GA26074@elte.hu> (raw)
In-Reply-To: <200710120053.20202.rc.poison@gmail.com>
* poison <rc.poison@gmail.com> wrote:
> Also the transfer rate didn't degrade too much for copying directly
> from reiserfs to reiserfs and not using encfs:
>
> dd if=/mnt/.backup/2CpGkrxvz6wgA0b0xloz8PavzMLrMymOgi9 of=/mnt/.tdata/test
> 1033+0 records in
> 1033+0 records out
> 1083179008 bytes (1.1 GB) copied, 16.9303 s, 64.0 MB/s
>
> Plus the transfer rate doesn't increase if I start a CPU hog while
> copying between reiserfs.
>
> So it looks more to me like theres a bad interaction between the new
> scheduler, fuse and encfs ...
i have no quick ideas - the behavior you are seeing is quite unexpected.
Could you try the current sched-devel code:
http://redhat.com/~mingo/cfs-scheduler/devel/sched-devel-combo-v2.6.23.patch
since this version of CFS does various things differently then the one
in v2.6.23, lets see whether perturbing it makes any difference to your
throughput.
you could also try the scheduler backport to v2.6.22.10, at:
http://redhat.com/~mingo/cfs-scheduler/
that would establish whether it's the changes in scheduling that cause
this or something else. Plus please enable CONFIG_SCHED_DEBUG and
CONFIG_SCHEDSTATS and run this debug script while such a transfer is
going on:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
and send me the resulting file.
Ingo
next prev parent reply other threads:[~2007-10-12 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:09 linux-2.6.23 - acting funny Helmut Toplizer
2007-10-11 22:53 ` poison
2007-10-12 6:05 ` Ingo Molnar [this message]
2007-10-14 20:55 ` poison
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 2:30 poison
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=20071012060516.GA26074@elte.hu \
--to=mingo@elte.hu \
--cc=bgrpt@toplitzer.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rc.poison@gmail.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