public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: poison <rc.poison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.23 - acting funny
Date: Sun, 14 Oct 2007 22:55:11 +0200	[thread overview]
Message-ID: <200710142255.11806.rc.poison@gmail.com> (raw)
In-Reply-To: <20071012060516.GA26074@elte.hu>

Hi and thanks for your reply :)

On Friday 12 October 2007, you wrote:
> 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.patc
>h
Maybe I messed something up. I first applied that patch and tested. Then 
reversed the patch with patch -R ... but in both cases the output of the 
cfs-debug-info script contained:
Sched Debug Version: v0.05-v20

>
> 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.
Without Hog: ~15MB/s
With Hog: ~19/MBs


>
> you could also try the scheduler backport to v2.6.22.10, at:
>
>   http://redhat.com/~mingo/cfs-scheduler/
with sched-cfs-v2.6.22.9-v22.patch applied to 2.6.22.10 (I didn't spot one for 
2.6.22.10):
Without Hog: ~14MB/s
With Hog: ~19MB/s

>
> 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.
I created one for each tested kernel with
$ while true; do echo test>/dev/null; done
running and without.

I'll send you the files in private.
Thanks for your time.

Regards,
 Andreas




  reply	other threads:[~2007-10-14 20:55 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
2007-10-14 20:55     ` poison [this message]
  -- 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=200710142255.11806.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