Message boards : BOINC client : BOINC V5.8.x Computer Info/Listings Bugs
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 16 Mar 07 Posts: 16 ![]() |
I recently switched all my Systems to V5.8.11 (some to 5.8.15) and noted the following : - Computer Listings now include lots of additional CPU Information (while useful for BOINC itself to have it, does it really belong all there ?) Differences across Operating Systems : Windows2000 SP4 AuthenticAMD AMD Athlon(tm) XP 3000+ [x86 Family 6 Model 10 Stepping 0] [fpu tsc sse 3dnow mmx] Linux (2.4.x upto 2.6.15 Kernel, various Distributions) AuthenticAMD AMD Athlon(tm) XP 3000+ [fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow] Linux (Fedora Core 6 - 2.6.18 and 2.6.20 Kernel) AuthenticAMD ---------------------- Windows Systems list Family/Model/Stepping, but only a few CPU Extensions. Various Linux Systems upto 2.6.15 Kernel list only the CPU Extensions, but there it lists just about... everything. My Fedora Core 6 Systems however, show only CPU Manufacturer and that's it (?) (have this on three separate Systems running FC6, fresh & clean installs) Note : BOINCview V1.4.2b which oversees the entire Network sees the CPU Identifiction correctly on the FC 6 Systems, so BOINC 5.8.x is reading/using it there - it just fails to report it into the Computer listing. ----------------- Apart from the additional Info completely clogging up the Computer Listing pages, I believe this is a Bug worth looking into. If there's anyone able to help me get the CPU Listings sorted out on FC 6, this would be great :) (otherwise, I'll soon have all Systems listed "incognito") ![]() |
Send message Joined: 15 Mar 07 Posts: 20 ![]() |
This is not a bug of BOINC, it's a bug of the OS... Well not really. BOINC doesn't test every extension, because that would take a bit. It just asks the OS what extensions it thinks it has. Since Windows 2000 knows nothing of SSE2 or above, you will not see those. |
![]() Send message Joined: 16 Mar 07 Posts: 16 ![]() |
Hm, I still would like the Extensions not to appear in the Project's Computer Listings, as it can be alot. Would be nice to at least have it filtered there downto the most basic ones (i.e. MMX, 3dNow, SSE-SSE3). They could be otherwise kept in a separate Line in the client_state.xml, i.e. Line <cpuflags> ------------ Not as important as the CPU Vendor-only bug anyway. (I have no clue, the data is present in the client_state.xml, it just doesn't make it into the Computer Listings of the Projects) ![]() |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
Moving to a separate field <cpuflags> is a good idea, but it's too late for that. There are lots of clients in the wild using the p_vendor field for the flags, so servers would still have to handle both. Not worth the hassle. Web view on projects could filter the flags out, though. That needs the projects to upgrade their servers when the filtering feature is added, and we know not all will do it. |
![]() Send message Joined: 16 Mar 07 Posts: 16 ![]() |
Understood, I guess that's anyway just a minor cosmetic problem. So, any insights as to why everything after CPU Vendor is omitted (although correctly listed in the client_state.xml) on Fedora Core 6 ? (I will test Fedora Core 7 RC2 next month, when I upgrade another System, maybe that works out) ![]() |
![]() Send message Joined: 12 Mar 07 Posts: 59 |
Moving to a separate field <cpuflags> is a good idea, but it's too late for that. There are lots of clients in the wild using the p_vendor field for the flags, so servers would still have to handle both. Not worth the hassle. Still worth doing, IMO, so long as the filtering is not a lot of work to write (and it doesn't sound like it is). It might even be worth making the filtering show only those fields that that project is interested in. R~~ |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.