So it sounds like we may have a test platform, which leaves the question of
repair
George: can you give us some idea of what was broken and/or pointers on what
needs to be done to repair it?
On Apr 25, 2014, at 4:34 AM, Adrian Reber wrote:
> On Fri, Apr 25, 2014 at 10:29:36AM +, Jeff Squ
So long as this isn't a requirement, I don't see an issue with standardizing
the syntax. I suspect Jeff's concern is with hard-coding ompi_info (and all its
flavors) with an option that looks for a specific MCA param from every
component. Seems somewhat icky from a software design standpoint, an
On Apr 24, 2014, at 9:41 PM, Mike Dubman wrote:
> not a requirement of course, but warm recommendation. Like you mentioned:
> "component developers who choose to expose such information do so using the
> suggested syntax, then that is a different proposal."
>
> >>>FWIW: we do not (and cannot,
Hi!
> I'm the original developer. The patch never got merged, but I have patches to
> some branches. Which version are you using?
For now, I'm not sticking to any specific version, I have spent last 3 days
trying to adapt patches from mosix.org to 1.6.X, but without significant
success :)
Whic
On Fri, Apr 25, 2014 at 10:29:36AM +, Jeff Squyres (jsquyres) wrote:
> On Apr 25, 2014, at 6:13 AM, Gilles Gouaillardet
> wrote:
>
> > it is possible to use qemu in order to emulate unavailable hardware.
> > for what it's worth, i am now running a ppc64 qemu emulated virtual
> > machine on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Although the one Mike suggests would be much easier for "end users", I
think that in this
case, if the end user is more of a Linux newbie, they would have scripts
written for them,
that the admins use or will be handed to them. Either way would be a
g
On Apr 25, 2014, at 7:01 AM, Mike Dubman wrote:
> >>>ompi_info --all --parsable | egrep ':(compile|run)time_version'
>
> yep, this is much better, but I don`t think we should count on end-user to be
> unix regex guru.
I thought you said this was for support scripts?
Users can easily do this:
>>>ompi_info --all --parsable | egrep ':(compile|run)time_version'
yep, this is much better, but I don`t think we should count on end-user to
be unix regex guru.
Ideally, following would be much user-friendlier:
ompi_info --all --parsable --print-sys-libs-versions
On Fri, Apr 25, 2014 at 1:32
On Apr 24, 2014, at 1:38 AM, Mike Dubman wrote:
> ** prefix each well-known MCA param with "print_":
I like the overall idea of this RFC, but I'm not wild about this specific word
"print" -- it seems weird. All the MCA parameters are *printed* -- the word
"print" doesn't really distinguish an
On Apr 25, 2014, at 6:13 AM, Gilles Gouaillardet
wrote:
> it is possible to use qemu in order to emulate unavailable hardware.
> for what it's worth, i am now running a ppc64 qemu emulated virtual
> machine on an x86_64 workstation.
> this is pretty slow (2 hours for configure and even more for
Jeff and all,
On 2014/04/25 18:47, Jeff Squyres (jsquyres) wrote:
> But ask that question a little differently: which is more complicated,
> long-term maintenance of a feature which no one really tests (or even
> has the hardware setup to test) or removal?
it is possible to use qemu in order to e
I'm the original developer. The patch never got merged, but I have patches
to some branches. Which version are you using?
On 24 Apr 2014 19:07, "Pavel V. Kaygorodov" wrote:
> Hi!
>
> What is current status of mosix support in OpenMPI?
> I have tried patches from
> http://www.cs.huji.ac.il/wikis/M
On Apr 24, 2014, at 10:47 PM, Ralph Castain wrote:
>> And, as George pointed out, I see a trend towards heterogeneity in
>> HPC, to I'd say this feature will be rather more important in the
>> future.
>
> We have been hearing about such "trends" for a long time, but have yet to see
> them actua
Also, the reason for rfc is this:
https://svn.open-mpi.org/trac/ompi/ticket/4556#comment:5
On Fri, Apr 25, 2014 at 7:41 AM, Mike Dubman wrote:
> not a requirement of course, but warm recommendation. Like you mentioned:
> "component developers who choose to expose such information do so using
>
not a requirement of course, but warm recommendation. Like you mentioned:
"component developers who choose to expose such information do so using the
suggested syntax, then that is a different proposal."
>>>FWIW: we do not (and cannot, for licensing reasons) link against Slurm,
so please don't inc
15 matches
Mail list logo
