From: Matt Mackall <mpm@selenic.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
ck@vds.kolivas.org
Subject: Re: RSDL-mm 0.28
Date: Sat, 10 Mar 2007 22:01:32 -0600 [thread overview]
Message-ID: <20070311040132.GS10394@waste.org> (raw)
In-Reply-To: <8cd998d50703101828l71fbec7bi9a819ad7b7fd9828@mail.gmail.com>
On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
> >make -j 5 ccache
> > beryl ok good awful
> > galeon good good bad
> > mp3 good good bad
> > terminal good good bad/ok
> > mouse good good bad/ok
...
> >RSDL makes most of the noyield hit back in normal make and then some
> >with ccache. Impressive. But ccache is still destroying interactivity
> >somehow. The ccache effect is fairly visible even with non-parallel
> >'make'.
>
> Ok I don't think there's any actual accounting problem here per se
> (although I did just recently post a bugfix for rsdl however I think
> that's unrelated). What I think is going on in the ccache testcase is
> that all the work is being offloaded to kernel threads reading/writing
> to/from the filesystem and the make is not getting any actual cpu
> time.
I don't see significant system time while this is happening.
> This is "worked around" in mainline thanks to the testing for
> sleeping on uninterruptible sleep in the interactivity estimator. What
> I suspect is happening is kernel threads that are running nice -5 are
> doing all the work on make's behalf in the setting of ccache since it
> is mostly i/o bound. The reason for -nice values on kernel threads is
> questionable anyway. Can you try renicing your kernel threads all to
> nice 0 and see what effect that has? Obviously this doesn't need a
> recompile, but is simple enough to implement in kthread code as a new
> default.
Sorry, little to no benefit.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-03-11 4:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 1:35 RSDL-mm 0.28 Matt Mackall
2007-03-11 2:28 ` Con Kolivas
2007-03-11 3:16 ` Andrew Morton
2007-03-11 3:43 ` William Lee Irwin III
2007-03-11 3:59 ` Con Kolivas
2007-03-11 3:39 ` Andrew Morton
2007-03-11 3:44 ` Con Kolivas
2007-03-11 4:01 ` Matt Mackall [this message]
2007-03-11 4:03 ` Matt Mackall
2007-03-11 6:19 ` Con Kolivas
2007-03-12 5:38 ` RSDL for 2.6.21-rc3- 0.29 Gene Heskett
2007-03-12 5:48 ` Con Kolivas
2007-03-12 6:37 ` Gene Heskett
2007-03-12 10:04 ` Gene Heskett
2007-03-12 12:51 ` Douglas McNaught
2007-03-12 18:28 ` Gene Heskett
2007-03-12 18:46 ` Douglas McNaught
2007-03-12 19:10 ` Gene Heskett
2007-03-12 19:14 ` Lee Revell
2007-03-12 19:43 ` Douglas McNaught
2007-03-12 19:54 ` Patrick Mau
2007-03-12 20:24 ` Gene Heskett
2007-03-13 1:32 ` Stracing Amanda (was: RSDL for 2.6.21-rc3- 0.29) Douglas McNaught
2007-03-13 2:39 ` Gene Heskett
2007-03-13 3:01 ` Nish Aravamudan
2007-03-13 4:04 ` Gene Heskett
2007-03-13 4:45 ` Willy Tarreau
2007-03-13 5:48 ` Gene Heskett
2007-03-12 13:22 ` RSDL-mm 0.28 David Schwartz
2007-03-12 14:54 ` Ray Lee
2007-03-13 7:22 ` Nick Piggin
2007-03-11 7:32 ` Willy Tarreau
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=20070311040132.GS10394@waste.org \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox