From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: Dave Chinner <dgc@sgi.com>, Nathan Scott <nathans@sgi.com>,
Steve Lord <lord@xfs.org>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
Christoph Hellwig <hch@infradead.org>
Subject: Re: RT and XFS
Date: Fri, 15 Jul 2005 12:23:11 +0200 [thread overview]
Message-ID: <20050715102311.GA5302@elte.hu> (raw)
In-Reply-To: <1121314226.14816.18.camel@c-67-188-6-232.hsd1.ca.comcast.net>
* Daniel Walker <dwalker@mvista.com> wrote:
> PI is always good, cause it allows the tracking of what is high
> priority , and what is not .
that's just plain wrong. PI might be good if one cares about priorities
and worst-case latencies, but most of the time the kernel is plain good
enough and we dont care. PI can also be pretty expensive. So in no way,
shape or form can PI be "always good".
Ingo
next prev parent reply other threads:[~2005-07-15 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 23:01 RT and XFS Daniel Walker
2005-07-12 23:39 ` William Weston
2005-07-13 0:25 ` Nathan Scott
2005-07-13 0:41 ` Daniel Walker
2005-07-13 0:37 ` Nathan Scott
2005-07-13 6:47 ` Ingo Molnar
2005-07-13 16:45 ` Daniel Walker
2005-07-14 0:22 ` Nathan Scott
2005-07-14 3:50 ` Dave Chinner
2005-07-14 4:10 ` Daniel Walker
[not found] ` <20050714052347.GA18813@elte.hu>
2005-07-14 15:56 ` Daniel Walker
2005-07-14 16:08 ` Christoph Hellwig
2005-07-18 12:10 ` Esben Nielsen
2005-07-19 3:26 ` Bill Huey
2005-07-19 12:34 ` Ingo Molnar
2005-07-19 13:27 ` Christoph Hellwig
2005-07-19 13:50 ` Ingo Molnar
2005-07-14 16:08 ` Christoph Hellwig
2005-07-15 10:23 ` Ingo Molnar [this message]
2005-07-15 16:16 ` Daniel Walker
2005-07-18 11:33 ` Esben Nielsen
2005-07-19 3:31 ` Bill Huey
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=20050715102311.GA5302@elte.hu \
--to=mingo@elte.hu \
--cc=dgc@sgi.com \
--cc=dwalker@mvista.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@xfs.org \
--cc=nathans@sgi.com \
/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