From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O10int for interactivity
Date: Mon, 28 Jul 2003 19:12:51 +0200 [thread overview]
Message-ID: <20030728171251.GA8605@localhost> (raw)
In-Reply-To: <20030728005543.0dca9531.akpm@osdl.org>
On Monday, 28 July 2003, at 00:55:43 -0700,
Andrew Morton wrote:
> There's a known problem with OpenOffice and its use of sched_yield().
> sched_yield() got changed in 2.6 and it makes OO unusable when there is
> other stuff happening.
>
> Apparently it has been fixed in recent OpenOffice versions. If you cannot
> reproduce this problem in any other application I'd be saying it is "not a
> bug".
>
This must be the reason behind a simple "Save..." of a little OpenOffice
Writer document taking 3 seconds with no activity on the box, and two
minutes when "make bzImage", or "yes" or anyhting CPU intensive.
On the other hand, OO saves files (which is a CPU-bound process) only
marginally slower under heavy hard disk read activity than on an idle
system. Tested with 2.6.0-test2 and with 2.6.0-test2 with latest
scheduler patch from Ingo (2.6.0-test1-G6).
Regards,
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.0-test1-bk3)
next prev parent reply other threads:[~2003-07-28 16:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 15:12 [PATCH] O10int for interactivity Con Kolivas
2003-07-27 16:26 ` Wade
2003-07-27 19:15 ` Felipe Alfaro Solana
2003-07-28 7:51 ` Wiktor Wodecki
2003-07-28 7:55 ` Andrew Morton
2003-07-28 8:00 ` Wiktor Wodecki
2003-07-28 17:12 ` Jose Luis Domingo Lopez [this message]
2003-07-28 18:08 ` Valdis.Kletnieks
2003-07-28 18:40 ` Andrew Morton
2003-07-28 21:29 ` Wiktor Wodecki
2003-07-28 21:35 ` Andrew Morton
2003-07-31 6:36 ` Nick Piggin
2003-07-31 7:43 ` Con Kolivas
2003-07-31 7:58 ` Nick Piggin
2003-07-31 14:59 ` Jamie Lokier
2003-07-31 15:24 ` Oliver Neukum
2003-07-31 15:40 ` Jamie Lokier
2003-07-31 22:56 ` Nick Piggin
2003-08-04 18:51 ` [PATCH] O13int " Felipe Alfaro Solana
2003-08-04 18:58 ` Felipe Alfaro Solana
2003-08-04 21:46 ` Con Kolivas
2003-08-04 22:16 ` Felipe Alfaro Solana
2003-07-29 14:21 ` [PATCH] O10int " Timothy Miller
2003-07-29 14:35 ` Con Kolivas
2003-07-29 15:35 ` Timothy Miller
2003-07-30 1:16 ` Diego Calleja García
2003-07-30 1:36 ` Con Kolivas
2003-07-30 19:28 ` aradorlinux
2003-07-30 19:34 ` Andrew Morton
2003-07-29 15:28 ` Valdis.Kletnieks
2003-07-29 15:44 ` Timothy Miller
2003-07-29 15:45 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2003-07-27 19:50 Voluspa
2003-07-28 2:05 Voluspa
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=20030728171251.GA8605@localhost \
--to=linux-kernel@24x7linux.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.