public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Perchine <dyp@perchine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NT soon to surpass Linux in specweb99 performance?
Date: Fri, 2 Feb 2001 02:03:09 +0600	[thread overview]
Message-ID: <01020202030905.00595@dyp.perchine.com> (raw)
In-Reply-To: <20010201143825.A21237@xi.linuxpower.cx> <3A79C156.A8F7FF58@dawa.demon.co.uk>
In-Reply-To: <3A79C156.A8F7FF58@dawa.demon.co.uk>

On Friday 02 February 2001 02:04, Paul Flinders wrote:
> Gregory Maxwell wrote:
> > Looks like TUX caught MS's attention:
> > http://www.spec.org/osg/web99/results/res2000q4/web99-20001211-00082.html
> >
> > Anyone know if their method of achieveing this is as flexible as TUX, or
> > is their "SWC 3.0" simply mean 'spec web cheat' and involve implimenting
> > the specweb dyanmic stuff in x86 assembly in their microkernel? :)
>
> Yeah, but Tux 2 is still faster on the same/similar hardware

Yeps. But there was no access time update turned off in its case. MS do this.

> http://www.spec.org/osg/web99/results/res2000q4/web99-20001127-00075.html

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01 19:38 NT soon to surpass Linux in specweb99 performance? Gregory Maxwell
2001-02-01 20:04 ` Paul Flinders
2001-02-01 20:03   ` Denis Perchine [this message]
2001-02-02 14:50   ` Michael Poole
2001-02-01 20:18 ` Walter Hofmann
2001-02-01 21:28 ` J Sloan

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=01020202030905.00595@dyp.perchine.com \
    --to=dyp@perchine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox