lkml.org 
[lkml]   [2002]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectMcVoy's Clusters (was Re: latest linus-2.5 BK broken)
    [ I removed half a dozen cc's on this, and am just sending to the
    list. Do people actually want the cc's?]

    Larry McVoy wrote:

    > > Checkpointing buys three things. The ability to preempt jobs, the
    > > ability to migrate processes,

    For large multi-processor systems, it isn't clear that those matter
    much. On single user systems I've tried , ps -ax | wc -l usually
    gives some number 50 < n < 100. For a multi-user general purpose
    system, my guess would be something under 50 system processes plus
    50 per user. So for a dozen to 20 users on a departmental server,
    under 1000. A server for a big application, like database or web,
    would have fewer users and more threads, but still only a few 100
    or at most, say 2000.

    So at something like 8 CPUs in a personal workstation and 128 or
    256 for a server, things average out to 8 processes per CPU, and
    it is not clear that process migration or any form of pre-emption
    beyond the usual kernel scheduling is needed.

    What combination of resources and loads do you think preemption
    and migration are need for?

    > > and the ability to recover from failed nodes, (assuming the
    > > failed hardware didn't corrupt your jobs checkpoint).

    That matters, but it isn't entirely clear that it needs to be done
    in the kernel. Things like databases and journalling filesystems
    already have their own mechanisms and it is not remarkably onerous
    to put them into applications where required.

    [big snip]

    > Larry McVoy's SMP Clusters
    >
    > Discussion on November 8, 2001
    >
    > Larry McVoy, Ted T'so, and Paul McKenney
    >
    > What is SMP Clusters?
    >
    > SMP Clusters is a method of partioning an SMP (symmetric
    > multiprocessing) machine's CPUs, memory, and I/O devices
    > so that multiple "OSlets" run on this machine. Each OSlet
    > owns and controls its partition. A given partition is
    > expected to contain from 4-8 CPUs, its share of memory,
    > and its share of I/O devices. A machine large enough to
    > have SMP Clusters profitably applied is expected to have
    > enough of the standard I/O adapters (e.g., ethernet,
    > SCSI, FC, etc.) so that each OSlet would have at least
    > one of each.

    I'm not sure whose definition this is:
    supercomputer: a device for converting compute-bound problems
    into I/O-bound problems
    but I suspect it is at least partially correct, and Beowulfs are
    sometimes just devices to convert them to network-bound problems.

    For a network-bound task like web serving, I can see a large
    payoff in having each OSlet doing its own I/O.

    However, in general I fail to see why each OSlet should have
    independent resources rather than something like using one to
    run a shared file system and another to handle the networking
    for everybody.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:26    [W:4.966 / U:0.304 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site