Claimed credit with dual CPUs?

ben
ben
Joined: 9 Feb 05
Posts: 36
Credit: 1,663
RAC: 0

> Do you know whether this

Message 7943 in response to message 7942

> Do you know whether this BOINC version is usable under wine-linux?
>
> Is this intended as a fix for both the dual-CPU problem & the
> hyperthreading problem?

Well, if regular 4.19 works, I believe mine should as well.

The benchmark/credit/dual CPU code is all regular c or c++ as is the rest of boinc, and only consist of 30 or so lines of code.

The only code that might misreport would be the CPU identification code (many more than 30 lines)...however if regular windows programs work I don't see why it should not.

ADDMP
ADDMP
Joined: 25 Feb 05
Posts: 104
Credit: 7,332,049
RAC: 0

> > Do you know whether this

Message 7944 in response to message 7943

> > Do you know whether this BOINC version is usable under wine-linux?
> >
> > Is this intended as a fix for both the dual-CPU problem & the
> > hyperthreading problem?
>
> Well, if regular 4.19 works, I believe mine should as well.

4.19 runs, but I would not say "works".
When I run 4.19 under wine-linux, it reports my operating system as "Microsoft Windows 95", and it reports my CPU as "Unknown CPU 586".

Win95, of course, does not support either dual CPUs or hyperthreading.

And the CPUs I am actually using are either single or dual Athlons, or a hyperthreading P4.

So on the face of it, 4.19 does not seem to have a clue as to either software or hardware. Unless it knows much more than it reports to me.

> The benchmark/credit/dual CPU code is all regular c or c++ as is the rest of
> boinc, and only consist of 30 or so lines of code.

> The only code that might misreport would be the CPU identification code (many
> more than 30 lines)...however if regular windows programs work I don't see why
> it should not.

ADDMP

ben
ben
Joined: 9 Feb 05
Posts: 36
Credit: 1,663
RAC: 0

> 4.19 runs, but I would not

Message 7945 in response to message 7944


> 4.19 runs, but I would not say "works".
> When I run 4.19 under wine-linux, it reports my operating system as "Microsoft
> Windows 95", and it reports my CPU as "Unknown CPU 586".
>
> Win95, of course, does not support either dual CPUs or hyperthreading.
>
> And the CPUs I am actually using are either single or dual Athlons, or a
> hyperthreading P4.
>
> So on the face of it, 4.19 does not seem to have a clue as to either software
> or hardware. Unless it knows much more than it reports to me.

Well,
When running under wine, the boinc program is getting its information about your computer strictly from Windows.

As such, if wine doesn't tell its running copy of windows that there are 2 or more CPUs, then that copy of windows can't tell BOINC about it.

Does the 4.24+ version of BOINC identify mutitple CPUs under wine? I suspect not...

Also, when running multiple threads BOINC.exe leaves all the details on how to manage threads up to windows...again if it doesn't know (via wine) it can't tell BOINC.

Paul D. Buck
Paul D. Buck
Joined: 17 Jan 05
Posts: 754
Credit: 5,385,205
RAC: 0

> > > Oh, lord, MORE

Message 7946 in response to message 7941

>
> > Oh, lord, MORE computers in my accounts I can't merge ...
>
> Paul ... Paul

Yes? I am listening ...

> 1. It will not require new host ID or merging of computers.

Um, ok ... what about this statement:

> 3. CPU name displayed on your list of "my computers" are more concise and accurate.

Every time that has happened, I get another copy of my computers and because the merge operation works on CPU name and OS name, I will have 3 copies of many of my computers ... none of which can be merged as they all have different CPU names ....

ben
ben
Joined: 9 Feb 05
Posts: 36
Credit: 1,663
RAC: 0

> Every time that has

Message 7947 in response to message 7946

> Every time that has happened, I get another copy of my computers and because
> the merge operation works on CPU name and OS name, I will have 3 copies of
> many of my computers ... none of which can be merged as they all have
> different CPU names ....

Paul,

If, after you used this code, you were to detach and also were to return to the original boinc_gui, and then re-attach to the project, you would create orphans.

However, to prove my case, simply look at my list of computers for SETI.
I doubt I could have gathered 70K of credit for one host since I rewrote parts of 4.19, and all my computers there just have their CPU names changed.

http://setiweb.ssl.berkeley.edu/hosts_user.php?userid=548863

ADDMP
ADDMP
Joined: 25 Feb 05
Posts: 104
Credit: 7,332,049
RAC: 0

> Well, > When running under

Message 7948 in response to message 7945

> Well,
> When running under wine, the boinc program is getting its information about
> your computer strictly from Windows.
>
> As such, if wine doesn't tell its running copy of windows that there are 2 or
> more CPUs, then that copy of windows can't tell BOINC about it.

Yeah, that seems to be the source of the claimed-points problem with wine.

> Does the 4.24+ version of BOINC identify mutitple CPUs under wine? I suspect
> not..

I have not been able to get it to install & run at all. I don't know whether anyone else has.

> Also, when running multiple threads BOINC.exe leaves all the details on how to
> manage threads up to windows...again if it doesn't know (via wine) it can't
> tell BOINC.

Right. But win-E@H does know somehow about thread management under wine-linux & uses two threads & efficiently calculates results that are validated as correct. So it seems that thread information & thread management is possible under wine. I have no idea how, of course, but someone around here does.

ADDMP

Keck_Komputers
Keck_Komputers
Joined: 18 Jan 05
Posts: 376
Credit: 5,744,455
RAC: 0

>Feedback please >on which

>Feedback please
>on which CPUs it identifies correctly and which it misses. (along with the
>entire incorrect name)

Although not exactly the feedback you are looking for, I have some.

DO NOT use this client with protien predictor. They have enough problems matching up computers for the homogenous redundancy using the standard client. Throw in a group of computers with non-standard CPU names and it will make their problems worse. Of course if you submit this code to the developers and it becomes the standard then everyone will have to update again with a new minimum required version.

BOINC WIKI

BOINCing since 2002/12/8

ben
ben
Joined: 9 Feb 05
Posts: 36
Credit: 1,663
RAC: 0

> DO NOT use this client with

Message 7950 in response to message 7949


> DO NOT use this client with protien predictor. They have enough problems
> matching up computers for the homogenous redundancy using the standard client.
> Throw in a group of computers with non-standard CPU names and it will make

Last I looked at the server source code, the only checks they were making were the presence of "Intel" "AMD" "Macintosh". And my change does, and gets WUs delivered/validated.

int CPU(SCHEDULER_REQUEST& sreq){
if ( strstr(sreq.host.p_vendor, "Intel") != NULL ) return Intel;
else if( strstr(sreq.host.p_vendor, "AMD") != NULL ) return AMD;
else if( strstr(sreq.host.p_vendor, "Macintosh") != NULL ) return Macintosh;
else return nocpu;
};

Jamie Plucinski
Jamie Plucinski
Joined: 25 Feb 05
Posts: 27
Credit: 17,460
RAC: 0

File now mirrored at

File now mirrored at www.jamieplucinski.co.uk/downloads/boinc_gui.exe Since I know how trashy freewebs can be :) e-mail me at jamieplucinski at hotmail.com if you want me to remove or update :P

Jamie Plucinski
Jamie Plucinski
Joined: 25 Feb 05
Posts: 27
Credit: 17,460
RAC: 0

Hi. Client identifies my

Hi. Client identifies my Athlon 64 3000+ as (Clawhammer), when it's labelled as a Newcastle on the AMD Box. What's up with that?

And how about an athlon 64 enhanced version? Since we all know AMD beats Intel on everything, except over-pricing their products, at that, Intel is king :P

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.