From: Antonio Vargas <wind@cocodriloo.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sean Neakums <sneakums@zork.net>, Andrew Morton <akpm@osdl.org>,
Con Kolivas <kernel@kolivas.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test1-mm1
Date: Wed, 16 Jul 2003 12:19:49 +0200 [thread overview]
Message-ID: <20030716101949.GE2684@wind.cocodriloo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307161052310.6193-100000@localhost.localdomain>
On Wed, Jul 16, 2003 at 10:55:52AM +0200, Ingo Molnar wrote:
>
> On Wed, 16 Jul 2003, Sean Neakums wrote:
>
> > [...] If I keep running 'ps aux' its output does start to become slow
> > again, snapping back to full speed after a few more runs. Kind of an
> > odd one.
>
> there was a similar bug in the gnome terminal code, it was a userspace X
> window-refresh/event-qeueing bug/race that was sensitive to scheduler
> timings. So it can go away and come back based on precise timings. Eg. it
> was more likely to happen with antialiasing turned on than off.
>
> Ingo
It always happened to me when I run "make menuconfig" under gnome-terminal on
redhat 9 with 2.5.73. Is it because of busy-waiting on a variable shared
amongst multiple processes/threads? If so, it smells of a bug in the application,
busy-waiting is _BAD_.
Greets, Antonio
--
In fact, this is all you need to know to be
a Caveman Database Programmer:
A relational database is a big spreadsheet
that several people can update simultaneously.
next prev parent reply other threads:[~2003-07-16 10:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 5:56 2.6.0-test1-mm1 Andrew Morton
2003-07-16 6:16 ` 2.6.0-test1-mm1 Joshua Kwan
2003-07-16 6:22 ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 8:07 ` 2.6.0-test1-mm1 Sean Neakums
2003-07-16 8:55 ` 2.6.0-test1-mm1 Ingo Molnar
2003-07-16 10:19 ` Antonio Vargas [this message]
2003-07-16 13:37 ` 2.6.0-test1-mm1 Helge Hafting
2003-07-16 14:24 ` 2.6.0-test1-mm1 Antonio Vargas
2003-07-16 9:15 ` 2.6.0-test1-mm1 Con Kolivas
2003-07-16 10:44 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 10:58 ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 12:24 ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 14:32 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 14:41 ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 15:02 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 15:09 ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 16:38 ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 14:03 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 12:53 ` 2.6.0-test1-mm1 Philippe Gramoullé
2003-07-16 17:21 ` 2.6.0-test1-mm1 Ramón Rey Vicente
2003-07-16 19:01 ` 2.6.0-test1-mm1 Zwane Mwaikambo
2003-07-16 23:25 ` 2.6.0-test1-mm1 Ramón Rey Vicente
2003-07-16 23:56 ` 2.6.0-test1-mm1 Zwane Mwaikambo
2003-07-16 22:02 ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:08 ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:17 ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:36 ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:56 ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-17 11:57 2.6.0-test1-mm1 Downing, Thomas
2003-07-20 18:50 2.6.0-test1-mm1 Downing, Thomas
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=20030716101949.GE2684@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=sneakums@zork.net \
/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;
as well as URLs for NNTP newsgroup(s).