From: Hugh Dickins <hugh@veritas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Denis Vlasenko <vda@ilport.com.ua>,
Chuck Ebbert <76306.1226@compuserve.com>,
"cutaway@bellsouth.net" <cutaway@bellsouth.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Coywolf Qi Hunt <coywolf@gmail.com>
Subject: Re: function ordering (was: Re: [RFC] exit_thread() speedups in x86 process.c)
Date: Mon, 4 Jul 2005 11:28:12 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0507041124140.11956@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050704092958.GA29325@infradead.org>
On Mon, 4 Jul 2005, Christoph Hellwig wrote:
> On Sun, Jul 03, 2005 at 01:30:23PM +0100, Hugh Dickins wrote:
> > > this way we don't need to put a lot of __slow's in the code *and* it's
> > > based on measurements not assumptions, and can be tuned for a specific
> > > situation in addition.
> >
> > This is reminiscent of "fur", whose source Old SCO opened.
> > Google for SCO fur: amidst all the hits about "fur flying"
> > you might find something useful!
>
> Was it? I was at Scaldera back in the days when it was supposed to get
> opensourced, but AFAIK it never actually happened, everyone just talked
> about it.
Look like you're right. Google shows me an announcement of intent,
and a man page, and an interesting gcc discussion; but no fur source.
Hugh
next prev parent reply other threads:[~2005-07-04 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 2:57 [RFC] exit_thread() speedups in x86 process.c Chuck Ebbert
2005-07-02 11:56 ` Denis Vlasenko
2005-07-03 11:45 ` function ordering (was: Re: [RFC] exit_thread() speedups in x86 process.c) Arjan van de Ven
2005-07-03 12:30 ` Hugh Dickins
2005-07-03 12:48 ` Arjan van de Ven
2005-07-04 9:29 ` Christoph Hellwig
2005-07-04 10:28 ` Hugh Dickins [this message]
2005-07-03 19:59 ` [RFC] exit_thread() speedups in x86 process.c cutaway
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=Pine.LNX.4.61.0507041124140.11956@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=76306.1226@compuserve.com \
--cc=arjan@infradead.org \
--cc=coywolf@gmail.com \
--cc=cutaway@bellsouth.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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
all inboxes | Powered by JetHome®