From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Scheduler experiences (with Reiser4 bug report)
Date: Wed, 08 Sep 2004 13:53:50 -0400 [thread overview]
Message-ID: <chngi1$tqc$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040905155502.GR26192@nysv.org>
Markus Törnqvist wrote:
> Yours truly wrote:
>
>>I haven't tried nicksched in a while, but it didn't perform as well as
>>Staircase.
>
>
> Just gave -rc1-mm3 a shot and had my filesystems say bad things.
> shrike kernel: reiser4 panicked cowardly: assertion failed: extent_get_start(ext) == extent_get_start(&uf_coord->extension.extent.extent)
> /bin/sh: line 1: 4407 Segmentation fault rm -f fs/xfs/.xfs_bmap.o.d
>
>
> Didn't get around to renicing X, but anyway, app launch time was longer
> and the music did twitch a bit when starting the simultaneous kernel
> and glibc compiles. So I'm still on Staircase and don't see any reason
> to change away.
>
> I retried running as much cpu-intensive stuff as I could on cko5, basically
> ck6, and everything was smooth. Respects to Con for that :)
>
> This is not a troll nor a flamebait, but an honest question.
> Should the need to re-nice X not be seen as broken behavior?
It would be desirable to have things run without doing that, people will
undoubtedly call it a bug or tuning, depending on point of view.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-09-08 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 12:14 Scheduler experiences Kasper Sandberg
2004-09-05 12:25 ` DaMouse
2004-09-05 12:37 ` Nick Piggin
2004-09-05 12:43 ` DaMouse
2004-09-05 12:56 ` Nick Piggin
2004-09-05 12:49 ` Piotr Neuman
2004-09-05 14:25 ` Markus Törnqvist
2004-09-05 15:55 ` Scheduler experiences (with Reiser4 bug report) mjt
2004-09-05 15:55 ` Markus Törnqvist
2004-09-05 16:07 ` Reiser4 bug mjt
2004-09-05 16:07 ` Markus Törnqvist
2004-09-08 17:53 ` Bill Davidsen [this message]
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='chngi1$tqc$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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.