public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Cyrus Massoumi <cyrusm@gmx.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Scalability to 48 cores
Date: Tue, 12 Oct 2010 00:55:23 +0200	[thread overview]
Message-ID: <201010120055.23602.diegocg@gmail.com> (raw)
In-Reply-To: <4CB381DB.1040206@gmx.net>

On Lunes, 11 de Octubre de 2010 23:30:03 Cyrus Massoumi escribió:
> A friend just sent me the following PDF about Linux Scalability to many cores and I thought it might be interesting to the list for further discussion.
> It's about scalability problems of the Linux kernel and applications with 48 and more cores.
> 
> http://pdos.csail.mit.edu/papers/linux:osdi10.pdf

Some of the contention points mentioned in Figure 1 seem to be the same
things that Nick Piggin is trying to solve with his VFS scalability
patchset.

  reply	other threads:[~2010-10-11 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 21:30 Kernel Scalability to 48 cores Cyrus Massoumi
2010-10-11 22:55 ` Diego Calleja [this message]
2010-10-12 14:33 ` Andi Kleen
2010-10-12 16:00   ` Theodore Tso
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=201010120055.23602.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --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