Re: cluster list

["J . A . Magallon" <jamagallon@able.es>]

On 03.01 Albert D. Cahalan wrote:
> 
> In that case, you have everything you need and no reason to even
> pay attention to this list. The existing stuff works fine.
>

But each one works its way. I thought this list will try to unify all
approaches in the base things they need.
BTW, i have been looking for a DSM implementation, and found none. And
bproc only works in 2.2.

> 
> Mine:
> 
> Each node consists of a CPU, local RAM, optional flash ROM, L3 cache,
> and a multi-purpose chip that does DMA between nodes. There isn't any
> expansion opportunity on the node, or even a PCI chip.
> 
> So stop assuming clusters have network cards! If I had one, it would
> be an add-on device accesed via a dumb (non-CPU) bridge node. There
> are some problems here too... which node(s) control(s) the device?
> Can (should) node 42 tell the device to use data in node 33?
>

Well, focus on that kind of special-purpose nodes and how many people will
test-use it, apart from you and your special-dma-chip supplier ?

I think about nodes connected by some link; the easiest is ethernet (if the
net is dedicated it does not to use tcp), but the communication device
sould be something configurable, say 'node, start cluster membership
on dev=xxx'.

If you boot each node diskless, clusterfs can read /etc/something
where the device is marked, and a map between 'address' (ip or whatever)
and node nunmber is given. In your case that map would be in flash, mine would
be on nfs.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.2-ac6 #1 SMP Wed Feb 28 01:53:51 CET 2001 i686


Linux-cluster: generic cluster infrastructure for Linux
Archive:       http://mail.nl.linux.org/linux-cluster/