Re: [BProc] Valgrind and BProc (again)

[Cerion Armour-B. <ce...@op...>]

On Monday 20 June 2005 12:27, Julian Seward wrote:
> I've been pondering a more generalised solution .. tell me if this
> sounds crazy.
>
> It's a modified version of bpsh (or a replacement).  Instead of
> doing
>
>    bpsh <node_specifiers> program args
>
> do
>
>    modified_bpsh <node_specifiers> path program args
>
> modified_bpsh reads the entire tree rooted at path into itself
> (mmap games, perhaps), migrates to the nodes, dumps the tree back
> into the node-local filesystem, and execs program w/args as usual.
>
> Running V on a slave node is then
>
>   modified_bpsh <node_specifiers>    \
>           /where/V/is/installed/on/master \               # the path
>           /where/V/is/installed/on/master/bin/valgrind \  # stage1
>           program \
>           args
>
> This strikes me as having several advantages:
>
> * doesn't require slaves to use an NFS-mounted filesystem
> * is useful for any kind of tool requiring a readonly filesystem
> * doesn't require linking V against BProc
>
> The intention is that the carried-around tree is small, as is indeed
> V's install tree is (5.7 M).  If bandwidth is an issue (fair enough, if
> sending copies to N hundred nodes) then it might be possible to
> compress the tree as it is read using a real-time compression package
> and decompress on the slaves.  I'm thinking of LZO
> (http://www.oberhumer.com/opensource/lzo) which is GPLd and very fast.
>
> Comments?
>
What about 'program'?
Are you imagining this to be in valgrind's install tree?
Else this would still have to be separately migrated, or on nfs, no?
C.