Michael ODonnell wrote:
>
>> Any suggestions to look for a 2^53 type problem?
>>
>
> Well, just for fun, how about going back to basics - what does this
> little program generate on all the systems in question?
>
>
> #include "stdio.h"
>
> main( int argc,
> char *argv[] )
> {
>
Ooops - I forgot about the void * ...
>> Any suggestions to look for a 2^53 type problem?
>
>Well, just for fun, how about going back to basics - what does this
>little program generate on all the systems in question?
#include "stdio.h"
main( int argc,
char *argv[] )
{
printf( "siz
> Any suggestions to look for a 2^53 type problem?
Well, just for fun, how about going back to basics - what does this
little program generate on all the systems in question?
#include "stdio.h"
main( int argc,
char *argv[] )
{
printf( "sizeof( double) %2u\n", sizeof(
Ben Scott writes:
> But it's funny, lots of people have disaster stories... it seems
> everyone knows what *not* to do, or what can go wrong... but if you
> ask what you *should* do, and people are less certain. :)
umm.. ya. speaking of what not to do, don't keep adding load to your
building tr
Dana Nowell wrote on 09/10/2009
05:06:24 PM:
> Bruce/Ben,
> I've some experience with binary oriented endian issues on about 15
> different platforms (Sun, SGI, Intel/AMD Windows PCs, Tandem/Compaq/HP
> NonStop 'mainframes', HP UX workstations, Linux, DEC Unix, and several
> flavors of Unix that
gnhlug-discuss-boun...@mail.gnhlug.org wrote on 09/10/2009 04:33:10 PM:
>
> Ben Scott writes:
>
> > We keep seeing the recommendation to use highly-portable encodings
> > when possible, e.g., ASCII, or some kind of self-descriptive encoding.
> > Which I fully agree is a very good idea.
> >
>
On Thu, Sep 10, 2009 at 5:06 PM, Dana Nowell
wrote:
> Which one is a bit more complex as this long winded post
> will hopefully show.
Thanks for that response; it's very informative!
> A typical 'standard' floating point network format is
> a sign bit followed by N exponent bits followed by M
Bruce/Ben,
I've some experience with binary oriented endian issues on about 15
different platforms (Sun, SGI, Intel/AMD Windows PCs, Tandem/Compaq/HP
NonStop 'mainframes', HP UX workstations, Linux, DEC Unix, and several
flavors of Unix that probably do not still exist). Basically INT signed
or un
On 09/10/2009 02:54 PM, Ben Scott wrote:
> What techniques, best practices,
> de facto standards, popular libraries, etc., exist for this sort of
> thing?
MPI was already mentioned:
http://www.open-mpi.org/faq/?category=supported-systems#heterogeneous-support
those guys are performance freaks.
Ben Scott writes:
> We keep seeing the recommendation to use highly-portable encodings
> when possible, e.g., ASCII, or some kind of self-descriptive encoding.
> Which I fully agree is a very good idea.
>
> But assume for the sake of discussion we want to keep overhead as
> low as possible
We keep seeing the recommendation to use highly-portable encodings
when possible, e.g., ASCII, or some kind of self-descriptive encoding.
Which I fully agree is a very good idea.
But assume for the sake of discussion we want to keep overhead as
low as possible for performance reasons, and "wa
On 09/10/2009 10:12 AM, Kevin D. Clark wrote:
> Bruce Labitt writes:
>
>
>> Kevin D. Clark wrote:
>>
>>> 2: Typically, binary stuff is sent over the network in "network byte
>>> order" and network byte order is big-endian. This statement is not
>>> universally agreed to -- in fact I used
Just an FYI, I've experienced some unpleasant problems with local serial
consoles breaking with Ubuntu Hardy under Xen 3.2 (xen-tools &
debootstrap). It may have a lot to do with the Debian Lenny host system
I was using though. If it's certified by Canonical and you can get
support you should be
On 09/09/2009 09:16 PM, Alan Johnson wrote:
> Good thought, but I don't think I'll have an issue there. I'm looking
> at less than 50 DomUs spread across 3-5 Dom0s. Still, it would be good
> to tuck that limit in the back of my head. Do you have it handy, or
> should I look it up?
Yeah, that's
gnhlug-discuss-boun...@mail.gnhlug.org wrote on 09/10/2009 10:12:12 AM:
>
> Bruce Labitt writes:
>
> > Kevin D. Clark wrote:
> > > 2: Typically, binary stuff is sent over the network in "network
byte
> > > order" and network byte order is big-endian. This statement is not
> > > universally ag
Bruce Labitt writes:
> Kevin D. Clark wrote:
> > 2: Typically, binary stuff is sent over the network in "network byte
> > order" and network byte order is big-endian. This statement is not
> > universally agreed to -- in fact I used to work at a shop where they'd
> > never even considered this
Sounds like a good explanation, but doesn't fit with my experience.
Several years ago I had a problem with my UPS refusing to let the
generator take over. It was a high quality (Honda) generator with more
than enough capacity and both 120 and 240 output. I suspected that the
problem was related t
Ben Scott wrote:
> Bruce accidentally sent this off-list, but said I could forward it
> here for benefit of all...
>
> Thanks again, Bruce, for the good info!
Thank you for the forward
>
> -- Forwarded message --
> From: Bruce Dawson
> Date: Wed, Sep 9, 2009 at 10:14 PM
>
Bruce accidentally sent this off-list, but said I could forward it
here for benefit of all...
Thanks again, Bruce, for the good info!
-- Forwarded message --
From: Bruce Dawson
Date: Wed, Sep 9, 2009 at 10:14 PM
Subject: Re: [OT] Generator testing
To: Ben Scott
Ben Scott wr
19 matches
Mail list logo
