public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Murray J. Root" <murrayr@brain.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>
Subject: Re: 2.6.0-test6 scheduling(?) oddness
Date: Wed, 01 Oct 2003 15:04:15 +1000	[thread overview]
Message-ID: <3F7A604F.1060905@cyberone.com.au> (raw)
In-Reply-To: <20030930215512.1df59be3.akpm@osdl.org>



Andrew Morton wrote:

>"Murray J. Root" <murrayr@brain.org> wrote:
>
>>The render finishes in the same 30 minutes, then oowriter starts.
>> oowriter takes about 3 seconds to load if no rendering is going on.
>>
>
>OpenOffice uses sched_yield() in strange ways which causes it to
>get hopelessly starved on 2.6 kernels.  I think RH have a fixed version,
>but I don't know if that has propagated into the upstream yet.
>
>

OK. Aside from the OpenOffice issue, you still have povray taking 50%
longer to complete, which is quite remarkable if its single threaded and
nothing else is running. Maybe its not the scheduler change? Anyway,
Con will want to know exactly which version of his scheduler you used in
test5 to check for possibilities.



  reply	other threads:[~2003-10-01  5:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  3:22 2.6.0-test6 scheduling(?) oddness Murray J. Root
2003-10-01  4:08 ` Nick Piggin
2003-10-01  4:09   ` Nick Piggin
2003-10-01  4:35   ` Murray J. Root
2003-10-01  4:55 ` Andrew Morton
2003-10-01  5:04   ` Nick Piggin [this message]
2003-10-01  5:18     ` Murray J. Root
2003-10-01  6:53       ` Andrew Morton
2003-10-01  7:19         ` Murray J. Root
2003-10-01  5:10   ` Murray J. Root
2003-10-01 21:47     ` bill davidsen
2003-10-01 22:30       ` Ed Sweetman
2003-10-06  2:29         ` bill davidsen
2003-10-06 17:02           ` Murray J. Root

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=3F7A604F.1060905@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=murrayr@brain.org \
    /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