From: Christoph Hellwig <hch@infradead.org>
To: Lori Gilbertson <loriann@sgi.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@osdl.org>,
lm@bitmover.com
Subject: Re: [PATCH]: Option to run cache reap in thread mode
Date: Wed, 16 Jun 2004 17:53:00 +0100 [thread overview]
Message-ID: <20040616165300.GA15411@infradead.org> (raw)
In-Reply-To: <200406161646.i5GGkO5e194114@theriver.americas.sgi.com>
On Wed, Jun 16, 2004 at 11:46:24AM -0500, Lori Gilbertson wrote:
> hch wrote:
>
> > Given you're @sgi.com address you probably know what
> > a freaking mess and maintaince nightmare IRIX has become because
> > of that.
>
> Hi Chris,
>
> I'm very curious about this comment - wondering what you base it
> on? I'm the engineering manager for IRIX real-time - we have
> no open bugs against it and have many customers depending on it.
> At least for the last 5 years had very low maintenance cost,
> mostly adding features, fixing a couple of bugs and producing new
> releases.
>
> Perhaps you would be so kind to let me know what led you to
> your statement?
Looks at the overhead of the normal IRIX sleeping locks vs linux spinlock
(and the priority inversion and sleeping locks arguments are the next one
I'll get from you I bet :)), talk to Jeremy how the HBA performance went
down when he had to switch the drivers to the sleeping locks, look at the
complexity of the irix scheduler with it's gazillions of special cases
(and yes, I think the current Linux scheduler is already to complex), or
the big mess with interrupt thread.
I've added Larry to the Cc list because he knows the IRIX internals much
better than I do (or at least did once) and has been warning of this move
that adds complexity to no end for all the special cases for at least five
years. He also had some nice IRIX vs Linux benchmarks when Linux on Indys
was new.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-06-16 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 14:24 Dimitri Sivanich
2004-06-16 15:29 ` Christoph Hellwig
2004-06-16 16:03 ` Dimitri Sivanich
2004-06-16 16:07 ` Christoph Hellwig
2004-06-16 16:25 ` Jesse Barnes
2004-06-16 16:51 ` Dimitri Sivanich
2004-06-16 16:46 ` Lori Gilbertson
2004-06-16 16:53 ` Christoph Hellwig [this message]
2004-06-16 21:30 ` Andrew Morton
2004-06-16 16:43 Mark_H_Johnson
[not found] <40D08225.6060900@colorfullife.com>
2004-06-16 18:02 ` Dimitri Sivanich
2004-06-16 18:58 ` Manfred Spraul
2004-06-17 13:10 ` Dimitri Sivanich
2004-06-18 4:40 ` Andrew Morton
2004-06-18 14:33 ` Dimitri Sivanich
2004-06-18 20:40 ` Andrew Morton
2004-06-18 21:04 ` Manfred Spraul
2004-06-18 21:44 ` Dimitri Sivanich
2004-06-18 22:03 ` Andrew Morton
[not found] <27JKg-4ht-11@gated-at.bofh.it>
[not found] ` <m3r7sfmq0r.fsf@averell.firstfloor.org>
2004-06-16 18:16 ` Dimitri Sivanich
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=20040616165300.GA15411@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lm@bitmover.com \
--cc=loriann@sgi.com \
--cc=sivanich@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