mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Andi Kleen <andi@firstfloor.org>
Cc: Cyrus Massoumi <cyrusm@gmx.net>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Scalability to 48 cores
Date: Tue, 12 Oct 2010 12:00:27 -0400	[thread overview]
Message-ID: <585FC89B-C279-485E-9AE4-6ABA0F5EE4CE@mit.edu> (raw)
In-Reply-To: <87wrpn1nwy.fsf@basil.nowhere.org>


On Oct 12, 2010, at 10:33 AM, Andi Kleen wrote:

> The paper is known, but it seems to be in the usual unproductive 
> "publish a paper, but don't care about fixing anything" acedemic mode.

The thing I found most disappointing about the paper is that it describe techniques that have been in use in industry to provide better scalability to commerical OS's, and which were first applied to Linux something like a decade ago.

Sure, at the time we were going to 4-16 way scalability, but the techniques used were known back then, and in fact the paper is actually pretty naive compared to what people at companies like Sequent had been doing for a very long time.

It's just that a lot of scalability work took a bit of a hiatus, oh, five years ago because at the time, Linux was good enough, and adding more scalability has costs (which is why not all of the changes SGI made for 512 and 1024-way scalability have not necessarily found their way into mainline).   The fact that we've needed to worry about scalability now that 6+ cores/socket are available now, and many more are coming soon, is something we've known for at least the last year or two. 

But since a lot of that work wasn't published in the appropriate hoidy-toidy "tenure-track" approved publication venues, to the academics, it didn't exist.

Oh, well....

-- Ted


  reply	other threads:[~2010-10-12 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 21:30 Cyrus Massoumi
2010-10-11 22:55 ` Diego Calleja
2010-10-12 14:33 ` Andi Kleen
2010-10-12 16:00   ` Theodore Tso [this message]
2010-10-12 17:02     ` Andi Kleen

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=585FC89B-C279-485E-9AE4-6ABA0F5EE4CE@mit.edu \
    --to=tytso@mit.edu \
    --cc=andi@firstfloor.org \
    --cc=cyrusm@gmx.net \
    --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

all inboxes | Powered by JetHome®