public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: poison <rc.poison@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: linux-2.6.23 - acting funny
Date: Thu, 11 Oct 2007 04:30:24 +0200	[thread overview]
Message-ID: <200710110430.25612.rc.poison@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 800 bytes --]

Hi :)
I have two harddisks with encfs on top of reiserfs between which I could copy 
data at ~22MB/s before the upgrade from 2.6.22 to 2.6.23. 
After the upgrade the transfer rate stuck at ~14MB/s and changing nice values 
did not help anything.

And now the funny part: 
I noticed the transfer rate go up to ~20MB/s when I startet compiling stuff. 
I just need to run a CPU hog like:
  while true; do echo test > /dev/null; done
and the transfer rate jumps from ~14MB/s to ~20MB/s.

top shows the two encfs processes with ~30%(read) and 50%(write) CPU usage no 
matter if I run the CPU hog or not.

Could this eventually be due to the new scheduler? Do I need to tune anything?

System: E6600, 4GB RAM, Slackware 12, config attached.
Do you need anything else?

PS: please CC me, I'm not subscribed

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 12696 bytes --]

             reply	other threads:[~2007-10-11  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  2:30 poison [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2007-10-14 20:55     ` 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=200710110430.25612.rc.poison@gmail.com \
    --to=rc.poison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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