Menu
▾
▴
iometer-devel — Dedicated for people who are contributing to the project / are interested in.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(17) |
Mar
(26) |
Apr
(3) |
May
(20) |
Jun
(3) |
Jul
(22) |
Aug
(15) |
Sep
(3) |
Oct
(12) |
Nov
(1) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(4) |
Feb
(11) |
Mar
(14) |
Apr
(48) |
May
(14) |
Jun
(24) |
Jul
(38) |
Aug
(17) |
Sep
(29) |
Oct
(13) |
Nov
(19) |
Dec
(21) |
| 2005 |
Jan
(16) |
Feb
(14) |
Mar
(23) |
Apr
(36) |
May
(15) |
Jun
(13) |
Jul
(39) |
Aug
(29) |
Sep
(5) |
Oct
(2) |
Nov
(13) |
Dec
(8) |
| 2006 |
Jan
(6) |
Feb
(12) |
Mar
(8) |
Apr
(34) |
May
(8) |
Jun
(36) |
Jul
(8) |
Aug
(22) |
Sep
(16) |
Oct
(54) |
Nov
(33) |
Dec
(16) |
| 2007 |
Jan
(8) |
Feb
(18) |
Mar
(6) |
Apr
|
May
(1) |
Jun
(12) |
Jul
(2) |
Aug
(10) |
Sep
(31) |
Oct
(1) |
Nov
(5) |
Dec
(3) |
| 2008 |
Jan
(3) |
Feb
(6) |
Mar
(33) |
Apr
(21) |
May
|
Jun
(8) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
(4) |
| 2009 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(12) |
Sep
(4) |
Oct
|
Nov
(4) |
Dec
(2) |
| 2011 |
Jan
(11) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(5) |
Aug
(3) |
Sep
(9) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(19) |
Mar
(7) |
Apr
(2) |
May
(7) |
Jun
|
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
(21) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <is...@ya...> - 2010-08-16 01:48:54
|
Hi All,
This is neto from Brazil
How are you?
First of All, I would like to thank you Joe, Ved and Daniel for all support and
help.
Now, my question is regarding: Linux (dynamo) behavior: Strange performance
numbers and bad performance using reads
I'm using latest Branch (but I already have had the same behavior with other
Iometer versions)
Windows - GUI
Linux - dynamo (Redhat 5.4 using dm-mp (multipathing) - Server with 64GB RAM.
Using FC (Fibre Channel) to connect to Storage Array.
Using writes (random writes) - performance is OK but the I/O numbers reported by
Iometer are not accurate. (Storage reports 500 IOPS and Iometer reports 200
IOPS)
Using reads (random reads) - performance is terrible. Using one worker or 50
workers the performance is the same. Increasing outstanding I/O doesn't help.
I have tried to recompile using O_DIRECT - same behavior.
Questions:
1) Why the numbers are not accurate?
2) Why do I have this "poor" performance on Linux (reads)? Writes are OK.
3) Outstanding I/O doesn't work on Linux. Why?
IMPORTANT: On Windows (dynamo) everything works as expected. :-)
Could you please help me to address those "questions"?
Thank you very much
All the best
neto
|
|
From: <jo...@ei...> - 2010-08-15 05:49:20
|
Neto, It is "just" a type checking error ;-) The current line looks like this: posix_memalign(&randomDataBuffer, sysconf(_SC_PAGESIZE), RANDOM_BUFFER_SIZE) change it to posix_memalign((void**)&randomDataBuffer, sysconf(_SC_PAGESIZE), RANDOM_BUFFER_SIZE) There are several other incantations that will work and a couple have a few other advantages so if the bug fix isn't exactly like above don't worry, it'll probably use a reinterpret_cast for better compile time checking. Good luck, Joe Quoting "is...@ya..." <is...@ya...>: > My friends > > Forgive me if I'm doing something wrong but... > > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer/ > > Copying all files ....................................................... > > Checked out revision 52. > > On Linux: > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1028: error: invalid conversion from âunsigned char**â > to âvoid**â > IOManager.cpp:1028: error: initializing argument 1 of âint > posix_memalign(void**, size_t, size_t)â > make: *** [IOManager.o] Error 1 > > Could you please help me? > > TIA > > neto > > > ________________________________ > From: "jo...@ei..." <jo...@ei...> > To: "is...@ya..." <is...@ya...> > Cc: Vedran Degoricija <ve...@ya...>; > iom...@li...; > iom...@li... > Sent: Sat, August 14, 2010 12:40:24 AM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > Neto, you're doing everything correctly. > > A quick look at the svn repo shows that the offending code was > introduced on March 26 by allenwa. > > If you go into the IOManager.cpp file and search for VirtualAlloc you > will find 2 instances, one with the problem code and one that is done > correctly. You can use this as an example to fix your problem. > > There should be series of #if defines for the various operating > systems, with Windows using VirtualAlloc and linux using valloc. You > will also need to fix the VirtualFree call in the stop test, it too > should be #ifdef'd > > If you go in to fix it up and submit a patch do me a favor and make > sure to change the VirtualAlloc call to check to make sure the > allocation actually succeeds (i.e. the data buffer is not NULL). > Sloppy practices like not checking only introduce hidden bugs waiting > to crash some innocent user. > > Good luck, > Joe > > > > Quoting "is...@ya..." <is...@ya...>: > >> I did: On Linux Redhat 5.4 >> >> svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer >> >> On Linux: WorkingBranch_Q2_2010_Release >> >> [root@localhost src]# make -f Makefile-Linux.x86_64 all >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp >> IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: >> IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope >> IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope >> IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope >> IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope >> IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: >> IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope >> IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope >> make: *** [IOManager.o] Error 1 >> >> >> >> >> ________________________________ >> From: Vedran Degoricija <ve...@ya...> >> To: "is...@ya..." <is...@ya...>; >> iom...@li...; >> iom...@li... >> Sent: Fri, August 13, 2010 5:42:56 PM >> Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release >> >> >> Hi Neto, >> >> The errors you are seeing are Windows definitions being compiled >> under Linux. >> What version are you trying to build and/or what SVN path did you sync with? >> >> All of the braches (trunk and tags included) should be buildable clean under >> Windows and Linux. >> >> Ved >> >> >> >> >> ________________________________ >> From: "is...@ya..." <is...@ya...> >> To: "is...@ya..." <is...@ya...>; >> iom...@li...; >> iom...@li... >> Sent: Fri, August 13, 2010 12:51:55 PM >> Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release >> >> >> Hi All, >> >> This is neto from Brazil >> >> How are you? >> >> Could you please someone help me to download the latest patch (svn track) of >> Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? >> >> Please this is urgent. >> >> TIA >> >> All the best >> >> neto >> >> >> >> >> ________________________________ >> From: "is...@ya..." <is...@ya...> >> To: iom...@li...; iom...@li... >> Sent: Fri, August 13, 2010 3:35:30 PM >> Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release >> >> >> Hi All, >> >> This is neto from Brazil >> >> How are you? >> >> >> svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer >> >> On Linux: WorkingBranch_Q2_2010_Release >> >> [root@localhost src]# make -f Makefile-Linux.x86_64 all >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp >> /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX >> -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE >> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX >> -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp >> IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: >> IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope >> IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope >> IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope >> IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope >> IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: >> IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope >> IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope >> make: *** [IOManager.o] Error 1 >> >> >> Any clues? >> >> All the best >> >> neto >> >> >> > > > |
|
From: <is...@ya...> - 2010-08-14 19:55:06
|
My friends Forgive me if I'm doing something wrong but... svn co https://iometer.svn.sourceforge.net/svnroot/iometer/ Copying all files ....................................................... Checked out revision 52. On Linux: [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1028: error: invalid conversion from âunsigned char**â to âvoid**â IOManager.cpp:1028: error: initializing argument 1 of âint posix_memalign(void**, size_t, size_t)â make: *** [IOManager.o] Error 1 Could you please help me? TIA neto ________________________________ From: "jo...@ei..." <jo...@ei...> To: "is...@ya..." <is...@ya...> Cc: Vedran Degoricija <ve...@ya...>; iom...@li...; iom...@li... Sent: Sat, August 14, 2010 12:40:24 AM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Neto, you're doing everything correctly. A quick look at the svn repo shows that the offending code was introduced on March 26 by allenwa. If you go into the IOManager.cpp file and search for VirtualAlloc you will find 2 instances, one with the problem code and one that is done correctly. You can use this as an example to fix your problem. There should be series of #if defines for the various operating systems, with Windows using VirtualAlloc and linux using valloc. You will also need to fix the VirtualFree call in the stop test, it too should be #ifdef'd If you go in to fix it up and submit a patch do me a favor and make sure to change the VirtualAlloc call to check to make sure the allocation actually succeeds (i.e. the data buffer is not NULL). Sloppy practices like not checking only introduce hidden bugs waiting to crash some innocent user. Good luck, Joe Quoting "is...@ya..." <is...@ya...>: > I did: On Linux Redhat 5.4 > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > > > ________________________________ > From: Vedran Degoricija <ve...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 5:42:56 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi Neto, > > The errors you are seeing are Windows definitions being compiled under Linux. > What version are you trying to build and/or what SVN path did you sync with? > > All of the braches (trunk and tags included) should be buildable clean under > Windows and Linux. > > Ved > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 12:51:55 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > Could you please someone help me to download the latest patch (svn track) of > Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? > > Please this is urgent. > > TIA > > All the best > > neto > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: iom...@li...; iom...@li... > Sent: Fri, August 13, 2010 3:35:30 PM > Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > Any clues? > > All the best > > neto > > > |
|
From: <is...@ya...> - 2010-08-14 19:39:18
|
My friends I need to compile for Windows and I don't have Visual C here Could you please help me ________________________________ From: "jo...@ei..." <jo...@ei...> To: "is...@ya..." <is...@ya...> Cc: Vedran Degoricija <ve...@ya...>; iom...@li...; iom...@li... Sent: Sat, August 14, 2010 12:40:24 AM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Neto, you're doing everything correctly. A quick look at the svn repo shows that the offending code was introduced on March 26 by allenwa. If you go into the IOManager.cpp file and search for VirtualAlloc you will find 2 instances, one with the problem code and one that is done correctly. You can use this as an example to fix your problem. There should be series of #if defines for the various operating systems, with Windows using VirtualAlloc and linux using valloc. You will also need to fix the VirtualFree call in the stop test, it too should be #ifdef'd If you go in to fix it up and submit a patch do me a favor and make sure to change the VirtualAlloc call to check to make sure the allocation actually succeeds (i.e. the data buffer is not NULL). Sloppy practices like not checking only introduce hidden bugs waiting to crash some innocent user. Good luck, Joe Quoting "is...@ya..." <is...@ya...>: > I did: On Linux Redhat 5.4 > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > > > ________________________________ > From: Vedran Degoricija <ve...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 5:42:56 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi Neto, > > The errors you are seeing are Windows definitions being compiled under Linux. > What version are you trying to build and/or what SVN path did you sync with? > > All of the braches (trunk and tags included) should be buildable clean under > Windows and Linux. > > Ved > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 12:51:55 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > Could you please someone help me to download the latest patch (svn track) of > Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? > > Please this is urgent. > > TIA > > All the best > > neto > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: iom...@li...; iom...@li... > Sent: Fri, August 13, 2010 3:35:30 PM > Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > Any clues? > > All the best > > neto > > > |
|
From: Vedran D. <ve...@ya...> - 2010-08-14 06:06:05
|
Joe, Thanks. It looks like I lied. This is new code that appears was not tested on unix yet. There are 2 spots in which it occurs: iomanager.cpp and iotargetdisk.cpp. Neto, I can make the fixes and submit them ASAP. Ved ________________________________ From: "jo...@ei..." <jo...@ei...> To: "is...@ya..." <is...@ya...> Cc: Vedran Degoricija <ve...@ya...>; iom...@li...; iom...@li... Sent: Fri, August 13, 2010 9:40:24 PM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Neto, you're doing everything correctly. A quick look at the svn repo shows that the offending code was introduced on March 26 by allenwa. If you go into the IOManager.cpp file and search for VirtualAlloc you will find 2 instances, one with the problem code and one that is done correctly. You can use this as an example to fix your problem. There should be series of #if defines for the various operating systems, with Windows using VirtualAlloc and linux using valloc. You will also need to fix the VirtualFree call in the stop test, it too should be #ifdef'd If you go in to fix it up and submit a patch do me a favor and make sure to change the VirtualAlloc call to check to make sure the allocation actually succeeds (i.e. the data buffer is not NULL). Sloppy practices like not checking only introduce hidden bugs waiting to crash some innocent user. Good luck, Joe Quoting "is...@ya..." <is...@ya...>: > I did: On Linux Redhat 5.4 > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > > > ________________________________ > From: Vedran Degoricija <ve...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 5:42:56 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi Neto, > > The errors you are seeing are Windows definitions being compiled under Linux. > What version are you trying to build and/or what SVN path did you sync with? > > All of the braches (trunk and tags included) should be buildable clean under > Windows and Linux. > > Ved > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 12:51:55 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > Could you please someone help me to download the latest patch (svn track) of > Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? > > Please this is urgent. > > TIA > > All the best > > neto > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: iom...@li...; iom...@li... > Sent: Fri, August 13, 2010 3:35:30 PM > Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > Any clues? > > All the best > > neto > > > |
|
From: <jo...@ei...> - 2010-08-14 05:07:13
|
Neto, you're doing everything correctly. A quick look at the svn repo shows that the offending code was introduced on March 26 by allenwa. If you go into the IOManager.cpp file and search for VirtualAlloc you will find 2 instances, one with the problem code and one that is done correctly. You can use this as an example to fix your problem. There should be series of #if defines for the various operating systems, with Windows using VirtualAlloc and linux using valloc. You will also need to fix the VirtualFree call in the stop test, it too should be #ifdef'd If you go in to fix it up and submit a patch do me a favor and make sure to change the VirtualAlloc call to check to make sure the allocation actually succeeds (i.e. the data buffer is not NULL). Sloppy practices like not checking only introduce hidden bugs waiting to crash some innocent user. Good luck, Joe Quoting "is...@ya..." <is...@ya...>: > I did: On Linux Redhat 5.4 > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > > > ________________________________ > From: Vedran Degoricija <ve...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 5:42:56 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi Neto, > > The errors you are seeing are Windows definitions being compiled under Linux. > What version are you trying to build and/or what SVN path did you sync with? > > All of the braches (trunk and tags included) should be buildable clean under > Windows and Linux. > > Ved > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: "is...@ya..." <is...@ya...>; > iom...@li...; > iom...@li... > Sent: Fri, August 13, 2010 12:51:55 PM > Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > Could you please someone help me to download the latest patch (svn track) of > Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? > > Please this is urgent. > > TIA > > All the best > > neto > > > > > ________________________________ > From: "is...@ya..." <is...@ya...> > To: iom...@li...; iom...@li... > Sent: Fri, August 13, 2010 3:35:30 PM > Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release > > > Hi All, > > This is neto from Brazil > > How are you? > > > svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer > > On Linux: WorkingBranch_Q2_2010_Release > > [root@localhost src]# make -f Makefile-Linux.x86_64 all > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp > /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX > -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX > -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp > IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: > IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope > IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope > IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope > IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope > IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: > IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope > IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope > make: *** [IOManager.o] Error 1 > > > Any clues? > > All the best > > neto > > > |
|
From: <is...@ya...> - 2010-08-14 00:16:37
|
I did: On Linux Redhat 5.4 svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer On Linux: WorkingBranch_Q2_2010_Release [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope make: *** [IOManager.o] Error 1 ________________________________ From: Vedran Degoricija <ve...@ya...> To: "is...@ya..." <is...@ya...>; iom...@li...; iom...@li... Sent: Fri, August 13, 2010 5:42:56 PM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi Neto, The errors you are seeing are Windows definitions being compiled under Linux. What version are you trying to build and/or what SVN path did you sync with? All of the braches (trunk and tags included) should be buildable clean under Windows and Linux. Ved ________________________________ From: "is...@ya..." <is...@ya...> To: "is...@ya..." <is...@ya...>; iom...@li...; iom...@li... Sent: Fri, August 13, 2010 12:51:55 PM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi All, This is neto from Brazil How are you? Could you please someone help me to download the latest patch (svn track) of Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? Please this is urgent. TIA All the best neto ________________________________ From: "is...@ya..." <is...@ya...> To: iom...@li...; iom...@li... Sent: Fri, August 13, 2010 3:35:30 PM Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi All, This is neto from Brazil How are you? svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer On Linux: WorkingBranch_Q2_2010_Release [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope make: *** [IOManager.o] Error 1 Any clues? All the best neto |
|
From: Vedran D. <ve...@ya...> - 2010-08-13 21:43:03
|
Hi Neto, The errors you are seeing are Windows definitions being compiled under Linux. What version are you trying to build and/or what SVN path did you sync with? All of the braches (trunk and tags included) should be buildable clean under Windows and Linux. Ved ________________________________ From: "is...@ya..." <is...@ya...> To: "is...@ya..." <is...@ya...>; iom...@li...; iom...@li... Sent: Fri, August 13, 2010 12:51:55 PM Subject: Re: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi All, This is neto from Brazil How are you? Could you please someone help me to download the latest patch (svn track) of Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? Please this is urgent. TIA All the best neto ________________________________ From: "is...@ya..." <is...@ya...> To: iom...@li...; iom...@li... Sent: Fri, August 13, 2010 3:35:30 PM Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi All, This is neto from Brazil How are you? svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer On Linux: WorkingBranch_Q2_2010_Release [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope make: *** [IOManager.o] Error 1 Any clues? All the best neto |
|
From: <is...@ya...> - 2010-08-13 19:52:02
|
Hi All, This is neto from Brazil How are you? Could you please someone help me to download the latest patch (svn track) of Iometer for Windows 64 bits and Linux 64 bits (RedHat 5.4)? Please this is urgent. TIA All the best neto ________________________________ From: "is...@ya..." <is...@ya...> To: iom...@li...; iom...@li... Sent: Fri, August 13, 2010 3:35:30 PM Subject: [Iometer-devel] Error compiling WorkingBranch_Q2_2010_Release Hi All, This is neto from Brazil How are you? svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer On Linux: WorkingBranch_Q2_2010_Release [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope make: *** [IOManager.o] Error 1 Any clues? All the best neto |
|
From: <is...@ya...> - 2010-08-13 19:35:37
|
Hi All, This is neto from Brazil How are you? svn co https://iometer.svn.sourceforge.net/svnroot/iometer iometer On Linux: WorkingBranch_Q2_2010_Release [root@localhost src]# make -f Makefile-Linux.x86_64 all /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOGlobals.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c Pulsar.cpp /usr/bin/g++ -O -Wall -D_GNU_SOURCE -DIOMTR_OSFAMILY_UNIX -DIOMTR_OS_LINUX -DIOMTR_CPU_X86_64 -DIOMTR_SETTING_GCC_M64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DNOMINMAX -DUSE_NEW_DISCOVERY_MECHANISM -DFORCE_STRUCT_ALIGN -c IOManager.cpp IOManager.cpp: In member function âvoid Manager::GenerateRandomData()â: IOManager.cpp:1023: error: âMEM_COMMITâ was not declared in this scope IOManager.cpp:1023: error: âMEM_RESERVEâ was not declared in this scope IOManager.cpp:1023: error: âPAGE_READWRITEâ was not declared in this scope IOManager.cpp:1023: error: âVirtualAllocâ was not declared in this scope IOManager.cpp: In member function âvoid Manager::Stop_Test(int)â: IOManager.cpp:1099: error: âMEM_RELEASEâ was not declared in this scope IOManager.cpp:1099: error: âVirtualFreeâ was not declared in this scope make: *** [IOManager.o] Error 1 Any clues? All the best neto |
|
From: Ben E. <ben...@sa...> - 2010-06-25 20:32:14
|
Ved, What is the status of your upcoming release? Would you say WorkingBranch_Q2_2010 is mostly stable? Ben From: Vedran Degoricija [mailto:ve...@ya...] Sent: Wednesday, May 26, 2010 10:47 AM To: Ben Englert; iom...@li... Subject: Re: [Iometer-devel] Patch submission from SandForce Hi Ben, For the benefit of the others on this distribution, and per our offline discussion, we can consider merging your code after we have completed the next major build. This will hopefully be in a few weeks. Thanks, Ved ________________________________ From: Ben Englert <ben...@sa...> To: "iom...@li..." <iom...@li...> Sent: Mon, May 24, 2010 2:49:40 PM Subject: [Iometer-devel] Patch submission from SandForce Iometer developers, I work for a company called SandForce. We are in the storage industry and have found Iometer very useful in assessing the performance of our products in the lab. We have added a few features to our internal version of Iometer that we’d like to contribute back to the main source tree, should you find them useful. Specifically, we have improved Iometer’s ability to simulate “real” disk load by capturing disk activity during such tasks as installing an operating system or running a database server, and then giving Iometer the ability to “play back” these loads from an input file. How should I proceed with regards to getting your input on these changes? Shall I generate a patch against your top-of-trunk source, and we can proceed from there? Thanks, Ben |
|
From: Vedran D. <ve...@ya...> - 2010-05-26 17:47:26
|
Hi Ben,
For the benefit of the others on this distribution, and per our offline discussion, we can consider merging your code after we have completed the next major build. This will hopefully be in a few weeks.
Thanks,
Ved
________________________________
From: Ben Englert <ben...@sa...>
To: "iom...@li..." <iom...@li...>
Sent: Mon, May 24, 2010 2:49:40 PM
Subject: [Iometer-devel] Patch submission from SandForce
Iometer developers,
I work for a company called SandForce. We are in the storage industry and have found Iometer very useful in assessing the performance of our products in the lab. We have added a few features to our internal version of Iometer that we’d like to contribute back to the main source tree, should you find them useful. Specifically, we have improved Iometer’s ability to simulate “real” disk load by capturing disk activity during such tasks as installing an operating system or running a database server, and then giving Iometer the ability to “play back” these loads from an input file.
How should I proceed with regards to getting your input on these changes? Shall I generate a patch against your top-of-trunk source, and we can proceed from there?
Thanks,
Ben
|
|
From: Ben E. <ben...@sa...> - 2010-05-24 22:02:22
|
Iometer developers, I work for a company called SandForce. We are in the storage industry and have found Iometer very useful in assessing the performance of our products in the lab. We have added a few features to our internal version of Iometer that we'd like to contribute back to the main source tree, should you find them useful. Specifically, we have improved Iometer's ability to simulate "real" disk load by capturing disk activity during such tasks as installing an operating system or running a database server, and then giving Iometer the ability to "play back" these loads from an input file. How should I proceed with regards to getting your input on these changes? Shall I generate a patch against your top-of-trunk source, and we can proceed from there? Thanks, Ben |
|
From: Daniel S. <dan...@ed...> - 2010-04-21 02:06:40
|
Dear Iometer developers, I'am happy to announce that there is now an Iometer Users group on LinkedIn. http://www.linkedin.com/groups?home=&gid=2976553 The idea is to complement our technical discussion on the mailing-list with a professional network for connecting with each other, sharing ideas and real world scenarios with like minded people, posting job opportunities and many more. Looking forward to see you there. Cheers, Daniel |
|
From: SourceForge.net <no...@so...> - 2010-03-10 09:21:38
|
Bugs item #2967273, was opened at 2010-03-10 09:21 Message generated for change (Tracker Item Submitted) made by gmxyr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=427254&aid=2967273&group_id=40179 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Gavin Martin (gmxyr) Assigned to: Nobody/Anonymous (nobody) Summary: Targets do not display in order Initial Comment: If you connect an enclosure with more that 12 targets it does not display the targets in the correct order, eg. it goes from 1 to 12 then you get target 20, then 2, etc. If you connect 48 target then you get number 48 at the top of the target list instead of at the bottom. This is with the latest RC1, on a 64bit platform. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=427254&aid=2967273&group_id=40179 |
|
From: <jo...@ei...> - 2009-02-12 04:28:49
|
Hey Luke, thanks for the concern. IOMeter doesn't care about sectors/LBAs, it deal with bytes (that gives you the ability to do misaligned transfers). When we are dealing with disks targets, the maximum disk size, the current transfers starting offset and ending offset are all unsigned 64bit values. So that means, theoretically, we can support 55bit LBAs or something like 16 exabytes, where a 16byte/32byte SCSI command can support 8 zettabytes. Now I say theoretically because there may be something that has been overlooked. But keep in mind that IOMeter has been used for a long time by many disk array manufacturers and I would be willing to bet some of them have gone quite large. My largest "raw" block device was a 16TB array, I did that under both linux and windows and I don't recall any major problems but that was 3 years ago or so. Maybe someone else will pipe in with a larger example. Hope this helps, Joe Quoting Luk...@se...: > > Does IOMeter support 34 Bit LBA's? (LBA ranges greater than 32 bits long) > > If not, are there any plans to make it so that it is able to do so? > > Eventually, drives are going to become larger than 2.14 Terabytes and will > support LBA addresses larger than 32 bits long. > > - Luke. > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the > power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Iometer-devel mailing list > Iom...@li... > https://lists.sourceforge.net/lists/listinfo/iometer-devel > |
|
From: <Luk...@se...> - 2009-02-11 17:02:51
|
Does IOMeter support 34 Bit LBA's? (LBA ranges greater than 32 bits long) If not, are there any plans to make it so that it is able to do so? Eventually, drives are going to become larger than 2.14 Terabytes and will support LBA addresses larger than 32 bits long. - Luke. |
|
From: Drews, P. <pau...@in...> - 2009-01-19 23:31:02
|
I just submitted bug 2521567 regarding failure of IOMETER to honor "Delay" parameter in Access Specifications that are used for network testing under Linux. In the cases I was testing, the delay was not honored; requests were sent out back-to-back with no intervening delay. From looking at the code, it appears that under some circumstances it MIGHT also be possible to have the delays honored, but with the CPU doing busy-wait during the idle time. In any case, I submitted a patch along with the bug report that fixes the problem, avoiding any busy-wait. This bug is against the current release candidate 2008-06-22-rc2. There doesn't seem to be much activity among the developers/forums/bug-tracker. Do I need to take any additional actions to get this bug-fix into a subsequent release or release candidate? - Paul Drews (pcdrews), Intel Corporation |
|
From: SourceForge.net <no...@so...> - 2009-01-19 23:23:12
|
Bugs item #2521567, was opened at 2009-01-19 15:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=427254&aid=2521567&group_id=40179 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Drews (pcdrews) Assigned to: Nobody/Anonymous (nobody) Summary: IOMETER not honoring "Delay" specs for network under Linux Initial Comment: When IOMETER waits, it does so at the lowest level by calling aio_suspend() with a timeout and a list of outstanding asynchronous Ios (so that it can handle/complete any Ios that complete while it is waiting). It turns out that there is an obscurely documented feature of aio_suspend(): if there are no actual outstanding Ios in the list, aio_suspend() returns immediately without an error and without waiting for the timeout time. IOMETER propagates this up as if it were a timeout. The top-level logic also erroneously concludes that the entire timeout has elapsed and returns from the "Delay" procedure immediately. I fixed the loop in the "delay" procedure to (1) do a regular sleep instead of a wait-for-io operation if there are no outstanding Ios, and (2) to keep on doing either kind of wait until the full delay time has elapsed. This problem was seen on the current 2008-06-22-rc2 release under Linux (Fedora 9) on an X86_64 platform. A patch that fixes the problem is as follows: Index: src/IOGrunt.cpp =================================================================== --- src.orig/IOGrunt.cpp +++ src/IOGrunt.cpp @@ -977,8 +977,22 @@ void Grunt::Asynchronous_Delay(int trans do { _ftime(&start_wait_time); - if (Complete_IO(transfer_delay) == ReturnTimeout) - return; + // Complete_IO ultimately calls aio_suspend(). If there are + // no outstanding IOs, aio_suspend returns immediately without + // an error and higher software layers turn the return into + // an apparent timeout. So if there are no oustanding IOs + // we should do a plain Sleep instead of a Complete_IO, + // because a Complete_IO would turn this into a busy-polling + // loop. + // + // Furthermore, even some IOs complete, we need to keep on + // going through this loop until the entire transfer_delay + // has been honored. + if (outstanding_ios > 0) { + Complete_IO(transfer_delay); + } else { + Sleep(transfer_delay); + } // More waiting is needed before allowing additional requests. _ftime(&end_wait_time); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=427254&aid=2521567&group_id=40179 |
|
From: Drews, P. <pau...@in...> - 2009-01-19 23:15:48
|
--> Paul Drews replies: I have posted a fix for this bug (1244848) in the bug-tracker entry (https://sourceforge.net/tracker/index.php?func=detail&aid=1244848&group_id=40179&atid=427254). The bug is present in the current release candidate 2008-06-22-rc2. There has not been much visible activity regarding this release candidate. Will this bug-fix magically get included in the next release candidate or release, or are there additional steps I should take? --> end paul We have been experimenting with IOMETER for Linux, for evaluating the interaction of power management with network traffic performance, and it works until we get into an endless loop of "*** Grunt thread exiting with 1 still active". It's not a big deal if we get one of those messages when the IOMETER control function stops the test, but if we get hundreds of messages ... the resulting statistics are no good. Is anyone using IOMETER with Linux for network performance testing? Do any of you know who did this work most recently, at Intel? There was an Intel contractor henryx.w.tieman@in... back in 2004, but he's not here any more. I have not found another micro-benchmark that lets you shape the traffic, and observe the BW / average response / maximum response. If IOMETER has been replaced by something more recent, we would like to know that. Thank you, Howard David and Paul Drews Intel Corp. / Corporate Technology Group / Systems Technology Lab |
|
From: <min...@gm...> - 2008-12-09 16:43:13
|
no. i do not have time to work on this any more... you can change the code to disable that dead loop as a work around. On Dec 8, 2008 9:12pm, "David, Howard" <how...@in...> wrote: > > > > > Was any progress made on #1244848? Cheung > Ming said he would follow up. I think we are seeing the same problem. > > Thank you, > > Howard David > > Intel Corp. > > > > [ > 1244848 ] *** Grunt thread exiting with 1 still active > > > > > > You may monitor this Tracker item after you log in > (register an account, > if you do not already have one) > > > > > > Submitted By: > > Marc Johnson - marcjohnson > > > > > Date Submitted: > > 2005-07-25 23:25 > > > > > > Last Updated By: > > cheungming - Comment added > > > > Date Last Updated: > > > 2005-08-16 02:19 > > > > > > Number of Comments: > > > 2 > > > > Number of Attachments: > > > 0 > > > > > > Category: (?) > > > None > > > > Group: (?) > > > None > > > > > > Assigned To: (?) > > > Nobody/Anonymous > > > > Priority: (?) > > > 5 > > > > > > Status: (?) > > > Open > > > > Resolution: (?) > > > None > > > > > > Summary: (?) > > > *** Grunt thread exiting with 1 still active > > > > > Private: (?) > > > No > > > > > > After running a network test, dynamo continuosly > > outputs to console: > > > > *** Grunt thread exiting with 1 still active > > *** Grunt thread exiting with 1 still active > > *** Grunt thread exiting with 1 still active > > > > ...and locks up the GUI (iometer). > > > > Ctrl-C'ing dynamo is the only way to unlock it. > > > > Built with iometer-2004.07.30-post.DS2, Makefile- > > Linux.x86_64. > > > > Linux lablx000 2.4.21-27.EL #1 SMP Wed Dec 1 > > 21:53:39 EST 2004 x86_64 x86_64 x86_64 GNU/Linux > > > > Any fixes for this? > > > > Thanks and please advise, > > Marc > > > > > > > > > > > > > > > > Followups: > > > > Comments > > > > > > > > > Date: 2005-08-16 02:19Sender: cheungmingLogged In: YES user_id=896657 this is caused by the bug fix on #1088486. the reason isthat a network io is differ from disk io. for diskio, theworker stops and then wait current io ends and quits, whichis pretty reasonable. but for network worker, it is possiblethat there is always 1 io unfinished for certain unknownreason, then it dead loop there. > > > > > > > > Date: 2005-07-27 13:36Sender: cheungmingLogged In: YES user_id=896657 Thanks for reporting. I will check this once get time. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: David, Howard > > Sent: Monday, December 08, 2008 > 6:03 PM > > To: > 'iom...@li...' > > Subject: IOMETER for Linux network > measurement ... "Grunt thread exiting with 1 still active" errors > > > > > > > > > We have been experimenting with IOMETER for Linux, for evaluating the > interaction of power management with network traffic performance, and it works > until we get into an endless loop of "*** Grunt thread exiting with 1 > still active". It's not a big deal if we get one of those messages > when the IOMETER control function stops the test, but if we get hundreds of > messages ... the resulting statistics are no good. > > > > > > Is anyone using IOMETER with Linux for network performance > testing? Do any of you know who did this work most recently, at > Intel? There was an Intel contractor hen...@in... back in > 2004, but he's not here any more. > > > > > > I have not found another micro-benchmark that lets you shape the > traffic, and observe the BW / average response / maximum response. If > IOMETER has been replaced by something more recent, we would like to know that. > > > > > > Thank you, > > > Howard David and Paul Drews > > > Intel Corp. / Corporate Technology Group / Systems Technology Lab > > > > > > > > > |
|
From: <min...@gm...> - 2008-12-09 16:43:10
|
no. i do not have time to work on this any more... you can change the code to disable that dead loop as a work around. On Dec 8, 2008 9:12pm, "David, Howard" <how...@in...> wrote: > > > > > Was any progress made on #1244848? Cheung > Ming said he would follow up. I think we are seeing the same problem. > > Thank you, > > Howard David > > Intel Corp. > > > > [ > 1244848 ] *** Grunt thread exiting with 1 still active > > > > > > You may monitor this Tracker item after you log in > (register an account, > if you do not already have one) > > > > > > Submitted By: > > Marc Johnson - marcjohnson > > > > > Date Submitted: > > 2005-07-25 23:25 > > > > > > Last Updated By: > > cheungming - Comment added > > > > Date Last Updated: > > > 2005-08-16 02:19 > > > > > > Number of Comments: > > > 2 > > > > Number of Attachments: > > > 0 > > > > > > Category: (?) > > > None > > > > Group: (?) > > > None > > > > > > Assigned To: (?) > > > Nobody/Anonymous > > > > Priority: (?) > > > 5 > > > > > > Status: (?) > > > Open > > > > Resolution: (?) > > > None > > > > > > Summary: (?) > > > *** Grunt thread exiting with 1 still active > > > > > Private: (?) > > > No > > > > > > After running a network test, dynamo continuosly > > outputs to console: > > > > *** Grunt thread exiting with 1 still active > > *** Grunt thread exiting with 1 still active > > *** Grunt thread exiting with 1 still active > > > > ...and locks up the GUI (iometer). > > > > Ctrl-C'ing dynamo is the only way to unlock it. > > > > Built with iometer-2004.07.30-post.DS2, Makefile- > > Linux.x86_64. > > > > Linux lablx000 2.4.21-27.EL #1 SMP Wed Dec 1 > > 21:53:39 EST 2004 x86_64 x86_64 x86_64 GNU/Linux > > > > Any fixes for this? > > > > Thanks and please advise, > > Marc > > > > > > > > > > > > > > > > Followups: > > > > Comments > > > > > > > > > Date: 2005-08-16 02:19Sender: cheungmingLogged In: YES user_id=896657 this is caused by the bug fix on #1088486. the reason isthat a network io is differ from disk io. for diskio, theworker stops and then wait current io ends and quits, whichis pretty reasonable. but for network worker, it is possiblethat there is always 1 io unfinished for certain unknownreason, then it dead loop there. > > > > > > > > Date: 2005-07-27 13:36Sender: cheungmingLogged In: YES user_id=896657 Thanks for reporting. I will check this once get time. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: David, Howard > > Sent: Monday, December 08, 2008 > 6:03 PM > > To: > 'iom...@li...' > > Subject: IOMETER for Linux network > measurement ... "Grunt thread exiting with 1 still active" errors > > > > > > > > > We have been experimenting with IOMETER for Linux, for evaluating the > interaction of power management with network traffic performance, and it works > until we get into an endless loop of "*** Grunt thread exiting with 1 > still active". It's not a big deal if we get one of those messages > when the IOMETER control function stops the test, but if we get hundreds of > messages ... the resulting statistics are no good. > > > > > > Is anyone using IOMETER with Linux for network performance > testing? Do any of you know who did this work most recently, at > Intel? There was an Intel contractor hen...@in... back in > 2004, but he's not here any more. > > > > > > I have not found another micro-benchmark that lets you shape the > traffic, and observe the BW / average response / maximum response. If > IOMETER has been replaced by something more recent, we would like to know that. > > > > > > Thank you, > > > Howard David and Paul Drews > > > Intel Corp. / Corporate Technology Group / Systems Technology Lab > > > > > > > > > |
|
From: David, H. <how...@in...> - 2008-12-09 02:09:12
|
We have been experimenting with IOMETER for Linux, for evaluating the interaction of power management with network traffic performance, and it works until we get into an endless loop of "*** Grunt thread exiting with 1 still active". It's not a big deal if we get one of those messages when the IOMETER control function stops the test, but if we get hundreds of messages ... the resulting statistics are no good. Is anyone using IOMETER with Linux for network performance testing? Do any of you know who did this work most recently, at Intel? There was an Intel contractor hen...@in... back in 2004, but he's not here any more. I have not found another micro-benchmark that lets you shape the traffic, and observe the BW / average response / maximum response. If IOMETER has been replaced by something more recent, we would like to know that. Thank you, Howard David and Paul Drews Intel Corp. / Corporate Technology Group / Systems Technology Lab |
|
From: ming z. <min...@gm...> - 2008-11-05 22:11:42
|
On Wed, Nov 5, 2008 at 4:25 PM, Wilson Kwong <wil...@ya...> wrote: > Hi there, > > I'm trying to see if there's a way to issue a payload pattern from IOMeter > even if the target drive becomes inactive/disconnected. I want to issue a > particular payload pattern when an error occurs such that an analyzer can > trigger on that pattern. However, it seems the Write and WriteFile functions > are based on the target_id, and if that targetted drive has failed, the > WriteFile in IOTargetDisk.cpp fails too. Is there a way around this such > that IOMeter will issue a pattern without a destination or with a 'fake' > destination? > not quite understand what you are trying to achieve. since you already read the source code, probably there is no such way, otherwise you might find it already. > > Thanks, > Wilson > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Iometer-devel mailing list > Iom...@li... > https://lists.sourceforge.net/lists/listinfo/iometer-devel > |
|
From: Wilson K. <wil...@ya...> - 2008-11-05 21:26:00
|
Hi there,
I'm trying to see if there's a way to issue a payload pattern from IOMeter even if the target drive becomes inactive/disconnected. I want to issue a particular payload pattern when an error occurs such that an analyzer can trigger on that pattern. However, it seems the Write and WriteFile functions are based on the target_id, and if that targetted drive has failed, the WriteFile in IOTargetDisk.cpp fails too. Is there a way around this such that IOMeter will issue a pattern without a destination or with a 'fake' destination?
Thanks,
Wilson
|
78 messages has been excluded from this view by a project administrator.
