From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] linux stats in last year from linuxcon
Date: Tue, 22 Sep 2009 10:17:26 -0400 [thread overview]
Message-ID: <3aaafc130909220717j55bc4f4br7d63e75c5f3578d5@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180909211812m8d29529u92fc2c4bbd05cba5@mail.gmail.com>
On Mon, Sep 21, 2009 at 9:12 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> it's on slashdot, it must be true:
>
> "During a roundtable discussion at LinuxCon in Portland, Oregon this
> afternoon, moderator and Novell distinguished engineer James Bottomley
> asked Tovalds whether Linux kernel features were being released too
> fast, before the kernel is stabilized.
>
> Citing an internal Intel study that tracked kernel releases, Bottomley
> said Linux performance had dropped about two per centage points at
> every release, for a cumulative drop of about 12 per cent over the
> last ten releases. "Is this a problem?" he asked.
>
> "We're getting bloated and huge. Yes, it's a problem," said Torvalds."
And instead of revising the design, I think we're going to see them go
for the 2-percent speedups here and there.
Another thing they won't consider is having separate versions for
high-end servers and PCs. I don't understand why Torvalds thinks Linux
has to be all things to all people.
>
> well, not really slashdot:
> http://www.theregister.co.uk/2009/09/22/linus_torvalds_linux_bloated_huge/
>
> Ron, did you throw anything at Linus while you were there? :)
>
>
next prev parent reply other threads:[~2009-09-22 14:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 16:22 ron minnich
2009-09-21 16:44 ` Patrick Kelly
2009-09-21 17:04 ` erik quanstrom
2009-09-21 17:29 ` Patrick Kelly
2009-09-21 17:02 ` tlaronde
2009-09-21 17:20 ` Patrick Kelly
2009-09-30 13:22 ` Ethan Grammatikidis
2009-09-21 17:41 ` Jack Norton
2009-09-21 17:53 ` Patrick Kelly
2009-09-21 19:32 ` David Leimbach
2009-09-21 19:42 ` Patrick Kelly
2009-09-22 1:12 ` andrey mirtchovski
2009-09-22 1:26 ` Patrick Kelly
2009-09-22 2:33 ` erik quanstrom
2009-09-22 2:52 ` andrey mirtchovski
2009-09-22 2:58 ` Patrick Kelly
2009-09-22 3:02 ` erik quanstrom
2009-09-22 6:15 ` Tim Newsham
2009-09-22 14:23 ` erik quanstrom
2009-09-22 16:57 ` Tim Newsham
2009-09-22 13:48 ` Eric Van Hensbergen
2009-09-22 14:44 ` David Leimbach
2009-09-22 14:39 ` David Leimbach
2009-09-22 14:47 ` erik quanstrom
2009-09-22 15:04 ` David Leimbach
2009-09-22 15:14 ` erik quanstrom
2009-09-22 16:26 ` David Leimbach
2009-09-22 3:36 ` ron minnich
2009-09-22 3:38 ` ron minnich
2009-09-22 14:17 ` J.R. Mauro [this message]
2009-09-22 14:47 ` David Leimbach
2009-09-22 20:14 ` Richard Uhtenwoldt
2009-09-22 20:47 ` Jack Norton
2009-09-22 22:31 ` Patrick Kelly
2009-09-23 1:55 ` David Arnold
2009-09-24 14:21 ` Patrick Kelly
2009-09-24 15:46 ` Jacob Todd
2009-09-24 15:56 ` Iruata Souza
2009-09-28 3:35 ` Patrick Kelly
2009-09-22 20:55 ` Chad Brown
[not found] <<Pine.BSI.4.64.0909220654020.23231@malasada.lava.net>
2009-09-22 17:13 ` erik quanstrom
2009-09-22 18:27 ` David Leimbach
2009-09-22 22:13 ` Tim Newsham
2009-09-22 22:25 ` Tim Newsham
2009-09-22 22:44 ` Jason Catena
[not found] <<012201ca3fec$c58f6020$50ae2060$@com>
2009-09-28 3:38 ` erik quanstrom
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=3aaafc130909220717j55bc4f4br7d63e75c5f3578d5@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).