From: "Pekka J Enberg" <penberg@cs.helsinki.fi>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Pekka Enberg <penberg@gmail.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Machine Freezes while Running Crossover Office
Date: Tue, 31 May 2005 09:35:45 +0300 [thread overview]
Message-ID: <courier.429C05C1.00005CC5@courier.cs.helsinki.fi> (raw)
In-Reply-To: <Pine.LNX.4.58.0505301024080.10545@ppc970.osdl.org>
On Mon, 2005-05-30 at 10:31 -0700, Linus Torvalds wrote:
> Also, pipes are a bit special from a scheduling standpoint because they
> use the magic "synchronous wakeup" thing, and it might be worthwhile
> trying to just change the two calls to "wake_up_interruptible_sync()" in
> fs/pipe.c to the non-sync version (ie just remove the "_sync" part).
Btw, I was looking at this yesterday but noticed there are no
__wake_up_sync() calls in the oprofile report. So I don't think we're
hitting the sync wakeup paths at all.
I also read Crossover sources a bit and I think the setup is something like
this:
wineserver:
- Polls a 'reply' pipe to see if there's something to read.
- If the pipe has something for us, read it.
- Do something and the write results to another pipe.
wine-preloader:
- Write to the 'reply' pipe.
- Read from the another pipe.
Looks if the processes keep on waking up each other and thus eat up all CPU
time. (Even more so if Crossover uses RT priority, have to check that.)
P.S. I can also verify that it is indeed the 64 KB change that breaks
Crossover. I changed PIPE_BUFFERS to 1 and could not reproduce the hang.
Increasing it to 8 makes the problem come up again.
Pekka
next prev parent reply other threads:[~2005-05-31 6:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 14:46 [PROBLEM] " Pekka Enberg
2005-05-29 18:12 ` Linus Torvalds
2005-05-29 18:20 ` Pekka Enberg
2005-05-29 18:49 ` Linus Torvalds
2005-05-29 20:49 ` Pekka Enberg
2005-05-29 22:59 ` Linus Torvalds
2005-05-29 23:06 ` Kyle Moffett
2005-05-30 15:23 ` Pekka Enberg
2005-05-30 17:31 ` Linus Torvalds
2005-05-30 18:07 ` Kyle Moffett
2005-05-30 18:22 ` Ingo Molnar
2005-05-30 18:22 ` Linus Torvalds
2005-05-30 18:25 ` Linus Torvalds
2005-05-30 19:12 ` Ingo Molnar
2005-05-31 13:54 ` Greg Stark
2005-05-31 6:15 ` Pekka J Enberg
2005-05-31 6:35 ` Pekka J Enberg [this message]
2005-05-31 6:54 ` Ingo Molnar
2005-05-31 16:53 ` Pekka Enberg
2005-05-31 17:24 ` Linus Torvalds
2005-05-31 18:41 ` Ingo Molnar
2005-05-31 21:20 ` Pekka Enberg
2005-06-01 0:07 ` Con Kolivas
2005-06-01 2:31 ` David Lang
2005-06-01 7:35 ` [patch] TASK_NONINTERACTIVE (was: Machine Freezes while Running Crossover Office) Ingo Molnar
2005-06-01 8:42 ` Pekka J Enberg
2005-06-01 8:55 ` [patch] " Con Kolivas
2005-06-01 10:26 ` Pekka J Enberg
2005-06-01 18:06 ` [patch] " Gene Heskett
2005-06-03 8:34 ` Pekka J Enberg
2005-06-03 10:57 ` Ingo Molnar
2005-06-07 13:14 ` Pekka Enberg
2005-10-17 15:10 ` [patch] " Pekka Enberg
2005-10-17 15:15 ` Ingo Molnar
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=courier.429C05C1.00005CC5@courier.cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@gmail.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®