iometer-devel — Dedicated for people who are contributing to the project / are interested in.

[Iometer-devel] IOmeter updates

[Vedran D. <ve...@ya...>]

Hi All,

I am not sure who is reading this or who is still interested in supporting the project. I've been MIA for a while as well, but I have a bit of time for some upkeep.

So, for those interested, I wanted to do the following:


  1.
Update the code and provide binaries for Windows and MacOS on arm64. What's the Linux status on this?
  2.
Cleanup the timer code around rdtsc and equivalents. OS timer routines are plenty good these days even virtualized. I don't want to speak for Linux here, so advise how you feel about it.
  3.
I'll take a look at some low hanging issues logged at sf.net and fix -  I think there are a couple of relevant ones.
  4.
Update arm64 binaries (based on 1.1.0) on sf.net but have all new source changes go to github going forward?

I have 1 and 2 (mostly) ready. I can push a branch and share binaries for review and testing. I can also go into more details on the above if there are questions.

Ved

Re: [Iometer-devel] Migrating Iometer code to Qt

[Vedran D. <ve...@ya...>]

+iometer-devel Thanks,Ved 

    On Thursday, December 3, 2015 7:12 AM, Jay Sanghavi <jay...@gm...> wrote:
 
 

 Hey,
     Thanks for the response. I just want to know how to use the port class specific functions in Qt . I tried using Q TCP socket communication but there is a drawback since I am not able to pass structure pointer via the socket. But in Visual Studio, they are using void pointer concept to interact. Is there any way I could be in Synchronization with developer team.
Regards,
Jay Sanghavi.On 03-Dec-2015 12:06 pm, "Vedran Degoricija" <ve...@ya...> wrote:

Hi Jay, Sorry for the late reply. Nobody has altered the MFC code much since the tool's inception. You might want to send this request out to the whole developer group as I have not been involved much lately. 
The short answer is that this is a complex undertaking where a re-write might be the right answer. :( Regards,Ved 


    On Thursday, October 22, 2015 12:24 PM, Jay Sanghavi <jay...@gm...> wrote:
 
 

 Hey Vedrand,
                      This is Jay Sanghavi working for Samsung R&D. I am working on migrating Iometer code in Qt. I am planning to make my own GUI in Qt and use dynamo.exe from the Iometer code. But there are some MFC components being used in the code.Can you please guide me through the process on how should I go about the Galileo App.


Regards,
Jay Sanghavi
Software Engineer at Samsung R&D

 
   


 
  

Re: [Iometer-devel] Edit IOMeter 1.1.0 RC to output IO traces to bin file and to accept IOs as a CMDline parameter

[Francis J. <fra...@gm...>]

Hi Karim,

My needs are real similar to your own. I am attempting to prep this version
of IOMeter for the same reason, getting ready for NVMe testing. Having the
ability to directly command IOMeter to execute a specific number of IOPs
would be way more accurate in terms of preconditioning the device and also
(i think) for fair testing for devices. Would you be able to share your
project as I would also like to become more familiar with tthe project in
the event I need to make other alterations to better suite my operation.

I am also under windows x64. Using Visual studio 12 to edit the project.

Thanks,

Francis

On Wed, Oct 14, 2015 at 2:31 AM, Gasmi Karim <kg...@2c...> wrote:

> Dear all
>
>
>
> Yes, daily, i have to use iometer for our validation tests, for now im
> testing 12 nvme intel p3700 together and try to reach 5Million IOPS like
> supermicro have done or quenta, that’s why do you have a good best practice
> and more explanations about the cmdline modifications and explanations
> about how we use and how it works.
>
>
>
> I’m under windows & linux
>
>
>
> Waiting your reply.
>
>
>
> Regards
>
>
>
> Karim
>
> 2CRSI
>
>
>
> *De :* Francis Jang [mailto:fra...@gm...]
> *Envoyé :* mardi 13 octobre 2015 20:34
> *À :* iom...@li...
> *Objet :* Re: [Iometer-devel] Edit IOMeter 1.1.0 RC to output IO traces
> to bin file and to accept IOs as a CMDline parameter
>
>
>
> Hi ladies and gents,
>
>
>
> Hope this day finds you all very well.  As my subject suggests I am in the
> process of altering the IOMeter project and came across a section that
> suggests contacting this group of fine people to see if it has already been
> done. I have altered the GalileoCmdLine files to allow the command line
> parameters. These are the remaining tasks:
>
> • IOs substitute timer – so test ends when total number of IOPs is achieved
>
> • Actual IOPs traces get output to a bin file
>
> If anyone one has the project that would be greatly appreciated!
>
>
>
> If you require more explanation please ping me.
>
>
>
> Many thanks for taking the time to read my email. I will be working on
> this in the meantime.
>
>
>
> BR,
>
>
>
> Francis
>
>
>
>
>
>
> ------------------------------
> [image: Avast logo] <http://www.avast.com/>
>
> L'absence de virus dans ce courrier électronique a été vérifiée par le
> logiciel antivirus Avast.
> www.avast.com
>
>

Re: [Iometer-devel] Edit IOMeter 1.1.0 RC to output IO traces to bin file and to accept IOs as a CMDline parameter

[Gasmi K. <kg...@2c...>]

Dear all

 

Yes, daily, i have to use iometer for our validation tests, for now im testing 12 nvme intel p3700 together and try to reach 5Million IOPS like supermicro have done or quenta, that’s why do you have a good best practice and more explanations about the cmdline modifications and explanations about how we use and how it works.

 

I’m under windows & linux

 

Waiting your reply.

 

Regards

 

Karim

2CRSI

 

De : Francis Jang [mailto:fra...@gm...] 
Envoyé : mardi 13 octobre 2015 20:34
À : iom...@li...
Objet : Re: [Iometer-devel] Edit IOMeter 1.1.0 RC to output IO traces to bin file and to accept IOs as a CMDline parameter

 

Hi ladies and gents,

 

Hope this day finds you all very well.  As my subject suggests I am in the process of altering the IOMeter project and came across a section that suggests contacting this group of fine people to see if it has already been done. I have altered the GalileoCmdLine files to allow the command line parameters. These are the remaining tasks:

• IOs substitute timer – so test ends when total number of IOPs is achieved

• Actual IOPs traces get output to a bin file

If anyone one has the project that would be greatly appreciated!

 

If you require more explanation please ping me.

 

Many thanks for taking the time to read my email. I will be working on this in the meantime.

 

BR,

 

Francis

 

 



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

Re: [Iometer-devel] Edit IOMeter 1.1.0 RC to output IO traces to bin file and to accept IOs as a CMDline parameter

[Francis J. <fra...@gm...>]

>
> Hi ladies and gents,
>
> Hope this day finds you all very well.  As my subject suggests I am in the
> process of altering the IOMeter project and came across a section that
> suggests contacting this group of fine people to see if it has already been
> done. I have altered the GalileoCmdLine files to allow the command line
> parameters. These are the remaining tasks:
> • IOs substitute timer – so test ends when total number of IOPs is
> achieved
> • Actual IOPs traces get output to a bin file
> If anyone one has the project that would be greatly appreciated!
>
> If you require more explanation please ping me.
>
> Many thanks for taking the time to read my email. I will be working on
> this in the meantime.
>
> BR,
>
> Francis
>
>

Re: [Iometer-devel] Iometer v1.1.0 for Linux

[Schmidlin, D. <dav...@in...>]

The IOMeter UI only runs on Windows.  If you want to use Linux then you will need to run the Dynamo on your Linux machine and connect it over a TCP/IP network to an IOMeter UI running on Windows.

-Dave

From: Wang, Philip [mailto:phi...@in...]
Sent: Tuesday, September 08, 2015 1:36 AM
To: 'iom...@li...'
Subject: [Iometer-devel] Iometer v1.1.0 for Linux

Hi,

I downloaded the v1.1.0 for Linux but there is only dynamo inside. Where can I find the whole package including Iometer? Thanks :)

I used the 2nd link below to download.

[cid:image001.png@01D0EA17.A070D180]

[Iometer-devel] Iometer v1.1.0 for Linux

[Wang, P. <phi...@in...>]

Hi,

I downloaded the v1.1.0 for Linux but there is only dynamo inside. Where can I find the whole package including Iometer? Thanks :)

I used the 2nd link below to download.

[cid:image001.png@01D0EA54.71B6C420]

[Iometer-devel] Visual Studio 2013 build?

[Muhammad A. <muh...@se...>]

Is there an effort underway to support building iometer with Visual Studio
2013 or in other words MSVC 12? And maybe with Unicode character set?

I attempted to build the trunk using VS 2013 after downloading
the Multibyte MFC Libraries and ran into a lot of compile errors, pointing
to the fact that the Multibyte character set support for MFC is depreciated
in Visual Studio 2013 [ref:
http://blogs.msdn.com/b/vcblog/archive/2013/07/08/mfc-support-for-mbcs-deprecated-in-visual-studio-2013.aspx]
& the port won't be trivial.

Thanks,
-Muhammad Ahmad

Re: [Iometer-devel] Run minimized

[Schmidlin, D. <dav...@in...>]

PW is 'abc123', Sorry about that.
-Dave

-----Original Message-----
From: Daniel Scheibli [mailto:da...@sc...] 
Sent: Saturday, March 07, 2015 3:18 AM
To: Schmidlin, David
Cc: iom...@li...
Subject: Re: [Iometer-devel] Run minimized

Hi David,

thank you very much for the patch. I tried to look at it, but it seems like the ZIP file has a password.

Best Regards,
Daniel



On 03/06/2015 10:57 PM, Schmidlin, David wrote:
> Attached is a proposed patch file for IOMeter that adds a parameter ‘S’ to configure IOMeter to run with the UI minimized.  This was done so that IOMeter executings using an ICF file could be done with-out the UI.
> 
>  
> 
> -David Schmidlin
> 
> 
> 
> ----------------------------------------------------------------------
> -------- Dive into the World of Parallel Programming The Go Parallel 
> Website, sponsored by Intel and developed in partnership with Slashdot 
> Media, is your hub for all things parallel software development, from 
> weekly thought leadership blogs to news, videos, case studies, 
> tutorials and more. Take a look and join the conversation now. 
> http://goparallel.sourceforge.net/
> 
> 
> 
> _______________________________________________
> Iometer-devel mailing list
> Iom...@li...
> https://lists.sourceforge.net/lists/listinfo/iometer-devel
> 

Re: [Iometer-devel] Run minimized

[Daniel S. <da...@sc...>]

Hi David,

thank you very much for the patch. I tried to look
at it, but it seems like the ZIP file has a password.

Best Regards,
Daniel



On 03/06/2015 10:57 PM, Schmidlin, David wrote:
> Attached is a proposed patch file for IOMeter that adds a parameter ‘S’ to configure IOMeter to run with the UI minimized.  This was done so that IOMeter executings using an ICF file could be done with-out the UI.
> 
>  
> 
> -David Schmidlin
> 
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> 
> 
> 
> _______________________________________________
> Iometer-devel mailing list
> Iom...@li...
> https://lists.sourceforge.net/lists/listinfo/iometer-devel
> 

[Iometer-devel] Run minimized

[Schmidlin, D. <dav...@in...>]

Attached is a proposed patch file for IOMeter that adds a parameter 'S' to configure IOMeter to run with the UI minimized.  This was done so that IOMeter executings using an ICF file could be done with-out the UI.

-David Schmidlin

[Iometer-devel] Patch proposal to explicitly set dynamo port

[Nicolas M. <nm...@gm...>]

Hello,

I needed iometer gui to connect back to Dynamo through a firewall
which was not possible because of the random generated port.

I modified the code and added an option to dynamo to get this
possible. I share it with you because I guess it can help others with
the same problem. I don't know if this the right way of doing this
though...

Option added : -r
If option is given, dynamo listening port is set to the parameter
given. If option is absent, a random port is generated like before.

The patch can be found in attachment.

Regards,
Nicolas Maupu

[Iometer-devel] IO meter with 520 sector size drives

[Girish D. <gir...@gm...>]

Hi,

I want to know if the IO meter support the 520 sector size drives? If not
how better are the chances to make code work by changing it? Also i see
that most of the windows /linux code is using the DeviceIOControl/linux aio
API which does not support the 520 block size drives. Does any body tried
this?

Regards,
Girish

[Iometer-devel] Odd Drive Type Issue and MSVS2k13 Compilation

[Ryan S. <ry...@rp...>]

I recently had an issue where 1.1.0 Dynamo would crash on my Win7x64
system.  I downloaded the source and was able to track the issue back
to a piece of cloud encryption software that created virtual drive
volumes within Windows.

I'm guessing this isn't the best nor the correct way to fix the
issue, but it fixed it enough for me to run it on my system. I found
quick_index to have a large negative value that then caused an access
violation error.  I just put a rough sanity check for the value and  all
seemed well enough for me to execute the software.  Here is the exact
change I made:

diff -ur iometer-1.1.0/src/IOManagerWin.cpp
iometer-1.1.0-rps/src/IOManagerWin.cpp
--- iometer-1.1.0/src/IOManagerWin.cpp 2013-08-20 18:09:26.000000000 -0500
+++ iometer-1.1.0-rps/src/IOManagerWin.cpp 2014-08-18 20:32:03.933430900 -0500
@@ -1758,7 +1758,7 @@
  // then fall back to slow search.

  int quick_index = mid_point +
GET_SDN_PTR(source[v].disk_info)->DeviceNumber + 1;
- if (EQUAL_DEVICE_NUMBERS(GET_SDN_PTR(source[v].disk_info),
GET_SDN_PTR(source[quick_index].disk_info)))
+ if (quick_index < 50 && quick_index > 0 &&
EQUAL_DEVICE_NUMBERS(GET_SDN_PTR(source[v].disk_info),
GET_SDN_PTR(source[quick_index].disk_info)))
  {
  PVOLUME_DISK_EXTENTS *pvde = GET_VDE_PTR(source[v].disk_info);
  PSTORAGE_DEVICE_NUMBER psdn = GET_SDN_PTR(source[v].disk_info);;


In addition, I had to make a few changes to get it to compile on MSVS2k13...

diff -ur iometer-1.1.0/src/msvs11/Dynamo.vcxproj
iometer-1.1.0-rps/src/msvs11/Dynamo.vcxproj
--- iometer-1.1.0/src/msvs11/Dynamo.vcxproj 2014-03-28 18:43:45.000000000 -0500
+++ iometer-1.1.0-rps/src/msvs11/Dynamo.vcxproj 2014-08-18
20:07:48.280172300 -0500
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<Project DefaultTargets="Build" ToolsVersion="4.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+<Project DefaultTargets="Build" ToolsVersion="12.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
   <ItemGroup Label="ProjectConfigurations">
     <ProjectConfiguration Include="Debug|Win32">
       <Configuration>Debug</Configuration>
@@ -25,26 +25,26 @@
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>Static</UseOfMfc>
     <UseOfAtl>false</UseOfAtl>
     <CharacterSet>NotSet</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>false</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Release|x64'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>false</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Debug|x64'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>false</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
@@ -97,7 +97,7 @@
     </Midl>
     <ClCompile>
       <Optimization>Disabled</Optimization>
-      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN32;IOMTR_CPU_I386;IOMTR_SETTING_CPU_AFFINITY;WINVER=0x0502;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_CONSOLE;_DEBUG;_DETAILS;%(PreprocessorDefinitions)</PreprocessorDefinitions>
+      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN32;IOMTR_CPU_I386;IOMTR_SETTING_CPU_AFFINITY;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_CONSOLE;_DEBUG;_DETAILS;%(PreprocessorDefinitions)</PreprocessorDefinitions>
       <BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
       <RuntimeLibrary>MultiThreadedDebug</RuntimeLibrary>
       <PrecompiledHeaderOutputFile>$(IntDir)Dynamo.pch</PrecompiledHeaderOutputFile>
@@ -134,7 +134,7 @@
     </Midl>
     <ClCompile>
       <Optimization>Disabled</Optimization>
-      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN64;IOMTR_CPU_X86_64;IOMTR_SETTING_CPU_AFFINITY;WINVER=0x0502;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_DEBUG;_CONSOLE;_DETAILS;%(PreprocessorDefinitions)</PreprocessorDefinitions>
+      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN64;IOMTR_CPU_X86_64;IOMTR_SETTING_CPU_AFFINITY;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_DEBUG;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions>
       <BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
       <RuntimeLibrary>MultiThreadedDebug</RuntimeLibrary>
       <PrecompiledHeaderOutputFile>$(IntDir)Dynamo.pch</PrecompiledHeaderOutputFile>
@@ -143,8 +143,10 @@
       <ProgramDataBaseFileName>$(IntDir)</ProgramDataBaseFileName>
       <BrowseInformation>true</BrowseInformation>
       <WarningLevel>Level4</WarningLevel>
-      <SuppressStartupBanner>true</SuppressStartupBanner>
+      <SuppressStartupBanner>false</SuppressStartupBanner>
       <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
+      <PreprocessToFile>false</PreprocessToFile>
+      <ShowIncludes>false</ShowIncludes>
     </ClCompile>
     <ResourceCompile>
       <PreprocessorDefinitions>_DEBUG;_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN32;IOMTR_CPU_I386;%(PreprocessorDefinitions)</PreprocessorDefinitions>
@@ -209,7 +211,7 @@
     </Midl>
     <ClCompile>
       <InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
-      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN64;IOMTR_CPU_X86_64;IOMTR_SETTING_CPU_AFFINITY;WINVER=0x0502;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions>
+      <PreprocessorDefinitions>_PULSAR_;IOMTR_OSFAMILY_WINDOWS;IOMTR_OS_WIN64;IOMTR_CPU_X86_64;IOMTR_SETTING_CPU_AFFINITY;USE_NEW_DISCOVERY_MECHANISM;FORCE_STRUCT_ALIGN;_CRT_SECURE_NO_DEPRECATE;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions>
       <StringPooling>true</StringPooling>
       <RuntimeLibrary>MultiThreaded</RuntimeLibrary>
       <FunctionLevelLinking>true</FunctionLevelLinking>
@@ -259,7 +261,9 @@
     <ClCompile Include="..\IOTargetVI.cpp" />
     <ClCompile Include="..\IOTime.cpp" />
     <ClCompile Include="..\IOVIPL.cpp" />
-    <ClCompile Include="..\NetTCP.cpp" />
+    <ClCompile Include="..\NetTCP.cpp">
+      <PreprocessToFile
Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">false</PreprocessToFile>
+    </ClCompile>
     <ClCompile Include="..\NetVI.cpp" />
     <ClCompile Include="..\Network.cpp" />
     <ClCompile Include="..\Pulsar.cpp" />
diff -ur iometer-1.1.0/src/msvs11/Iometer.vcxproj
iometer-1.1.0-rps/src/msvs11/Iometer.vcxproj
--- iometer-1.1.0/src/msvs11/Iometer.vcxproj 2014-03-28 18:43:45.000000000 -0500
+++ iometer-1.1.0-rps/src/msvs11/Iometer.vcxproj 2014-08-18
10:01:52.318081000 -0500
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<Project DefaultTargets="Build" ToolsVersion="4.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+<Project DefaultTargets="Build" ToolsVersion="12.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
   <ItemGroup Label="ProjectConfigurations">
     <ProjectConfiguration Include="Debug|Win32">
       <Configuration>Debug</Configuration>
@@ -26,25 +26,25 @@
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>Static</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>Static</UseOfMfc>
     <CharacterSet>NotSet</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Debug|x64'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>Static</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
   <PropertyGroup
Condition="'$(Configuration)|$(Platform)'=='Release|x64'"
Label="Configuration">
     <ConfigurationType>Application</ConfigurationType>
-    <PlatformToolset>v110</PlatformToolset>
+    <PlatformToolset>v120</PlatformToolset>
     <UseOfMfc>Static</UseOfMfc>
     <CharacterSet>MultiByte</CharacterSet>
   </PropertyGroup>
diff -ur iometer-1.1.0/src/NetTCP.cpp iometer-1.1.0-rps/src/NetTCP.cpp
--- iometer-1.1.0/src/NetTCP.cpp 2013-08-20 18:09:26.000000000 -0500
+++ iometer-1.1.0-rps/src/NetTCP.cpp 2014-08-18 13:13:04.159232700 -0500
@@ -75,6 +75,7 @@
 /* ##                                                                     ## */
 /* ######################################################################### */

+#include "StdAfx.h"

 #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
  #include <afx.h>
diff -ur iometer-1.1.0/src/Network.cpp iometer-1.1.0-rps/src/Network.cpp
--- iometer-1.1.0/src/Network.cpp 2013-08-20 18:09:26.000000000 -0500
+++ iometer-1.1.0-rps/src/Network.cpp 2014-08-18 13:26:35.102616100 -0500
@@ -71,6 +71,8 @@
 /* ##                                                                     ## */
 /* ######################################################################### */

+#include "StdAfx.h"
+
 #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
 #include <afx.h>
 #endif

Hope this is of use,
Ryan

-- 
Ryan P Sommers
ry...@rp...

Re: [Iometer-devel] LinkedIn group

[Daniel S. <da...@sc...>]

Hi Robert,

> Is anyone following the LinkedIn group for IOMeter?  

yes, I do.

> I did not see a release notice posted to the LinkedIn group for the latest release.
> I'm happy to do so.

great, please go ahead.

> When do we start planning the next release?  How are new features and enhancement 
> requests being tracked?  Are we using sourceforge or some other mechanism?

Timeline wise we release when we are ready. Content wise it depends on what
developers are interested in bringing forward. The evergreen of big topics
is the OS independent UI. Ideally we do this by cleaning up the network
protocol, so that even different implementations are thinkable (classical
UI, CLI, language binding?,...).

For tracking requests, SourceForge is currently the place.

Regards,
Daniel

[Iometer-devel] LinkedIn group

[Robert R. <rob...@gm...>]

Is anyone following the LinkedIn group for IOMeter?  I did not see a
release notice posted to the LinkedIn group for the latest release.  I'm
happy to do so.

When do we start planning the next release?  How are new features and
enhancement requests being tracked?  Are we using sourceforge or some other
mechanism?

Best regards,
Robert.

-- 
Robert Randall | rob...@gm...

[Iometer-devel] Version 1.1.0 released

[Daniel S. <da...@sc...>]

Dear all,

it has been a while since the last official stable release. So today
we are happy to announce the release of the Iometer 1.1.0 version.

There have been many changes.

Highlights are for instance the libaio support on Linux or the new
timer code on Windows & OS X. Also the data patterns have been extended
and the definition of fixed seeds got added to the random number
generator.

For a complete list of all the changes and bug files being added,
please refer to the CHANGELOG file.

Enjoy,
the Iometer team

Re: [Iometer-devel] The lastest updates and some more

[Larvoire, Jean-F. <jea...@hp...>]

Hi,

This still does not work for me with the targetver.h file that you sent me last week:

#pragma once

// Including SDKDDKVer.h defines the highest available Windows platform.

// If you wish to build your application for a previous Windows platform, include WinSDKVer.h and
// set the _WIN32_WINNT macro to the platform you wish to support before including SDKDDKVer.h.
#include <winsdkver.h>
#define _WIN32_WINNT _WIN32_WINNT_VISTA
#include <SDKDDKVer.h>

Instead, here’s the version from my Visual C++ “Hello” sample that works:

#pragma once

// The following macros define the minimum required platform.  The minimum required platform
// is the earliest version of Windows, Internet Explorer etc. that has the necessary features to run
// your application.  The macros work by enabling all features available on platform versions up to and
// including the version specified.

// Modify the following defines if you have to target a platform prior to the ones specified below.
// Refer to MSDN for the latest info on corresponding values for different platforms.
#ifndef _WIN32_WINNT            // Specifies that the minimum required platform is Windows Vista.
#define _WIN32_WINNT 0x0600     // Change this to the appropriate value to target other versions of Windows.
#endif

As far as I can tell, the two are equivalent, with yours just using a C macro from winsdkver.h (that mine can’t find) for the _WIN32_WINNT definition.

Jean-François

From: Vedran Degoricija [mailto:ve...@ya...]
Sent: Thursday, 23 January, 2014 23:14
To: Robert Randall; Larvoire, Jean-Francois
Cc: iom...@li...
Subject: Re: [Iometer-devel] The lastest updates and some more

Hi Jean-Francois,

You are right. I neglected to propagate the targetver.h header during my last check-in. This will be fixed today.

Thanks for the note on the additional capabilities. If you have sources modifications to share, I'd like to see them.  I cannot promise they will all be included or how soon.

Thanks!
Ved

On Thursday, January 23, 2014 7:54 AM, Robert Randall <rob...@gm...<mailto:rob...@gm...>> wrote:
Hi Jean,

The file is attached.  Sorry about that, my fault.

On Thu, Jan 23, 2014 at 9:46 AM, Larvoire, Jean-Francois <jea...@hp...<mailto:jea...@hp...>> wrote:
Hi,

I tried rebuilding the latest sources in Subversion.
FYI, this fails as it is:
Every C++ compilation fails with error:
StdAfx.h(80) : fatal error C1083: Cannot open include file: 'targetver.h': No such file or directory

Copying targetver.h from the “Hello” sample project in Visual Studio fixed the issue.
Still this file should be added into the Subversion tree.


Unrelated:

Last year, I implemented a few improvement for iometer, that I could contribute if you’re interested:

- Display the total number of assigned targets on the status bar. (Useful when manually selecting a large number of targets, to make sure the intended number of targets were indeed selected)
- Added a -l option to specify a log file. (Instead of accumulating error messages in popup windows as is done by default. I had storms with hundreds of popups that were really painful to close!)
- Added a -V option to display the program version on stdout and exit.
- Added a -? option to display a help screen on stdout and exit.
- Added a DEBUG_ENTRY() macro to log method calls in debug mode. (Useful to understand the sequence of events, but at the cost of making the debug version even slower.)

Jean-François

========================================================================
= Jean-François Larvoire                 =========   _/      ===========
= Hewlett-Packard                        =======    _/           =======
= 5 Avenue Raymond Chanas, Eybens        =====     _/_/_/  _/_/_/  =====
= 38053 Grenoble Cedex 9, FRANCE         =====    _/  _/  _/  _/   =====
= Phone: +33 480 32 02 33                =====   _/  _/  _/_/_/    =====
= Fax:   +33 476 14 43 05                =======        _/       =======
= Email: jea...@hp...<mailto:jea...@hp...>   ==========    _/     ==========
========================================================================


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Iometer-devel mailing list
Iom...@li...<mailto:Iom...@li...>
https://lists.sourceforge.net/lists/listinfo/iometer-devel



--
Robert Randall | rob...@gm...<mailto:rob...@gm...>

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk

_______________________________________________
Iometer-devel mailing list
Iom...@li...<mailto:Iom...@li...>
https://lists.sourceforge.net/lists/listinfo/iometer-devel

Re: [Iometer-devel] The lastest updates and some more

[Vedran D. <ve...@ya...>]

Hi Jean-Francois,
 
You are right. I neglected to propagate the targetver.h header during my last check-in. This will be fixed today.
 
Thanks for the note on the additional capabilities. If you have sources modifications to share, I'd like to see them.  I cannot promise they will all be included or how soon.
 
Thanks!
Ved



On Thursday, January 23, 2014 7:54 AM, Robert Randall <rob...@gm...> wrote:
  
Hi Jean,
>
>
>The file is attached.  Sorry about that, my fault.
>
>
>
>On Thu, Jan 23, 2014 at 9:46 AM, Larvoire, Jean-Francois <jea...@hp...> wrote:
>
>Hi, 
>>  
>>I tried rebuilding the latest sources in Subversion. 
>>FYI, this fails as it is: 
>>Every C++ compilation fails with error: 
>>StdAfx.h(80) : fatal error C1083: Cannot open include file: 'targetver.h': No such file or directory 
>>  
>>Copying targetver.h from the “Hello” sample project in Visual Studio fixed the issue. 
>>Still this file should be added into the Subversion tree. 
>>  
>>  
>>Unrelated: 
>>  
>>Last year, I implemented a few improvement for iometer, that I could contribute if you’re interested: 
>>  
>>- Display the total number of assigned targets on the status bar. (Useful when manually selecting a large number of targets, to make sure the intended number of targets were indeed selected) 
>>- Added a -l option to specify a log file. (Instead of accumulating error messages in popup windows as is done by default. I had storms with hundreds of popups that were really painful to close!) 
>>- Added a -V option to display the program version on stdout and exit. 
>>- Added a -? option to display a help screen on stdout and exit. 
>>- Added a DEBUG_ENTRY() macro to log method calls in debug mode. (Useful to understand the sequence of events, but at the cost of making the debug version even slower.) 
>>  
>>Jean-François 
>>  
>>======================================================================== 
>>= Jean-François Larvoire                 =========   _/      =========== 
>>= Hewlett-Packard                        =======    _/           ======= 
>>= 5 Avenue Raymond Chanas, Eybens        =====     _/_/_/  _/_/_/  ===== 
>>= 38053 Grenoble Cedex 9, FRANCE         =====    _/  _/  _/  _/   ===== 
>>= Phone: +33 480 32 02 33                =====   _/  _/  _/_/_/    ===== 
>>= Fax:   +33 476 14 43 05                =======        _/       ======= 
>>= Email: jea...@hp...   ==========    _/     ========== 
>>======================================================================== 
>>    
>>------------------------------------------------------------------------------
>>CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>Critical Workloads, Development Environments & Everything In Between.
>>Get a Quote or Start a Free Trial Today.
>>http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>>_______________________________________________
>>Iometer-devel mailing list
>>Iom...@li...
>>https://lists.sourceforge.net/lists/listinfo/iometer-devel
>>
>>
>
>
>
>-- 
>Robert Randall | rob...@gm... 
>
>------------------------------------------------------------------------------
>CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>Learn Why More Businesses Are Choosing CenturyLink Cloud For
>Critical Workloads, Development Environments & Everything In Between.
>Get a Quote or Start a Free Trial Today. 
>http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
>_______________________________________________
>Iometer-devel mailing list
>Iom...@li...
>https://lists.sourceforge.net/lists/listinfo/iometer-devel
>
>
>     

Re: [Iometer-devel] The lastest updates and some more

[Robert R. <rob...@gm...>]

Hi Jean,

The file is attached.  Sorry about that, my fault.


On Thu, Jan 23, 2014 at 9:46 AM, Larvoire, Jean-Francois <
jea...@hp...> wrote:

>  Hi,
>
>
>
> I tried rebuilding the latest sources in Subversion.
>
> FYI, this fails as it is:
>
> Every C++ compilation fails with error:
>
> StdAfx.h(80) : fatal error C1083: Cannot open include file: 'targetver.h':
> No such file or directory
>
>
>
> Copying targetver.h from the “Hello” sample project in Visual Studio fixed
> the issue.
>
> Still this file should be added into the Subversion tree.
>
>
>
>
>
> Unrelated:
>
>
>
> Last year, I implemented a few improvement for iometer, that I could
> contribute if you’re interested:
>
>
>
> - Display the total number of assigned targets on the status bar. (Useful
> when manually selecting a large number of targets, to make sure the
> intended number of targets were indeed selected)
>
> - Added a -l option to specify a log file. (Instead of accumulating error
> messages in popup windows as is done by default. I had storms with hundreds
> of popups that were really painful to close!)
>
> - Added a -V option to display the program version on stdout and exit.
>
> - Added a -? option to display a help screen on stdout and exit.
>
> - Added a DEBUG_ENTRY() macro to log method calls in debug mode. (Useful
> to understand the sequence of events, but at the cost of making the debug
> version even slower.)
>
>
>
> Jean-François
>
>
>
> ========================================================================
>
> = Jean-François Larvoire                 =========   _/      ===========
>
> = Hewlett-Packard                        =======    _/           =======
>
> = 5 Avenue Raymond Chanas, Eybens        =====     _/_/_/  _/_/_/  =====
>
> = 38053 Grenoble Cedex 9, FRANCE         =====    _/  _/  _/  _/   =====
>
> = Phone: +33 480 32 02 33                =====   _/  _/  _/_/_/    =====
>
> = Fax:   +33 476 14 43 05                =======        _/       =======
>
> = Email: jea...@hp...   ==========    _/     ==========
>
> ========================================================================
>
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Iometer-devel mailing list
> Iom...@li...
> https://lists.sourceforge.net/lists/listinfo/iometer-devel
>
>


-- 
Robert Randall | rob...@gm...

[Iometer-devel] The lastest updates and some more

[Larvoire, Jean-F. <jea...@hp...>]

Hi,

I tried rebuilding the latest sources in Subversion.
FYI, this fails as it is:
Every C++ compilation fails with error:
StdAfx.h(80) : fatal error C1083: Cannot open include file: 'targetver.h': No such file or directory

Copying targetver.h from the "Hello" sample project in Visual Studio fixed the issue.
Still this file should be added into the Subversion tree.


Unrelated:

Last year, I implemented a few improvement for iometer, that I could contribute if you're interested:

- Display the total number of assigned targets on the status bar. (Useful when manually selecting a large number of targets, to make sure the intended number of targets were indeed selected)
- Added a -l option to specify a log file. (Instead of accumulating error messages in popup windows as is done by default. I had storms with hundreds of popups that were really painful to close!)
- Added a -V option to display the program version on stdout and exit.
- Added a -? option to display a help screen on stdout and exit.
- Added a DEBUG_ENTRY() macro to log method calls in debug mode. (Useful to understand the sequence of events, but at the cost of making the debug version even slower.)

Jean-François

========================================================================
= Jean-François Larvoire                 =========   _/      ===========
= Hewlett-Packard                        =======    _/           =======
= 5 Avenue Raymond Chanas, Eybens        =====     _/_/_/  _/_/_/  =====
= 38053 Grenoble Cedex 9, FRANCE         =====    _/  _/  _/  _/   =====
= Phone: +33 480 32 02 33                =====   _/  _/  _/_/_/    =====
= Fax:   +33 476 14 43 05                =======        _/       =======
= Email: jea...@hp...<mailto:jea...@hp...>   ==========    _/     ==========
========================================================================

Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers interested?

[Vedran D. <ve...@ya...>]

Hi Robert,
 
I checked in my changes. The fix for the ICF loading is also there, see ManagerMap::SpawnLocalManagers() and please provide feedback.
 
Regards,
Ved



On Tuesday, January 21, 2014 6:04 AM, Robert Randall <rob...@gm...> wrote:
  
Hi Ved,
>
>
>Did you get a chance to merge my changes into the SVN trunk?  Did you want me to fix the multiple workers problem?
>
>
>Best,
>Robert
>
>
>
>On Fri, Jan 17, 2014 at 7:24 AM, Robert Randall <rob...@gm...> wrote:
>
>Hi Ved,
>>
>>
>>Please let me know when you've committed the changes to the trunk of the repository so I may update my local copy.  
>>
>>
>>The problem is simple to reproduce.  Start IOMeter and create a configuration with two managers and save the configuration file.  Restart IOMeter and load the configuration file.  One manager will start automatically and IOmeter will wait for the second manager but it is never started.  If you would like me to fix this just let me know. 
>>
>>
>>If you would like me to join the maintainers of IOMeter I am happy to do so.  I'm an very interested in improving the marketplace perception of IOMeter.  It feels like updating the GUI and authoring documentation on how IOMeter performs the its IO under each OS implementation of Dynamo to better inform users of the capabilities and sophistication of the application might be quite helpful to improving the perception of IOMeter. 
>>
>>
>>We need an evangelist for IOMeter.  It is good stuff but it has suffered from a lack of attention and that is sad.  I've used it for longer than I care to admit for both network and storage performance testing. 
>>
>>
>>Best regards,
>>Robert.
>>
>>
>>
>>On Thu, Jan 16, 2014 at 7:45 PM, Vedran Degoricija <ve...@ya...> wrote:
>>
>>Hi Robert,
>>> 
>>>Thank you. For the most part, it seems that the bVistaStyle piece addresses the assert on exit under the debugger. Thanks for the catch!  I also included most of your changes having to do stdafx cleanup.  Vistual Studio analyzer also caught a couple of interesting deletes that were missing the [] notation. I don't know if these would have been evident at runtime. 
>>> 
>>>Lastly, you mentioned and issue with loading multiple workers. Can you clarify that one please? I vaguely recall something about that, but it would help me to have all of the info. 
>>> 
>>>Thanks,
>>>Ved
>>>
>>>
>>>
>>>On Wednesday, January 15, 2014 6:13 AM, Robert Randall <rob...@gm...> wrote:
>>>  
>>>Hi Ved,
>>>>
>>>>
>>>>Zip file of my source tree is attached.  Please feel free to ask questions.
>>>>
>>>>
>>>>BR,
>>>>Robert
>>>>
>>>>
>>>>
>>>>On Wed, Jan 15, 2014 at 1:31 AM, Vedran Degoricija <ve...@ya...> wrote:
>>>>
>>>>Hi Robert,
>>>>> 
>>>>>(Apologies for calling you Randall earlier.)
>>>>> 
>>>>>I am having trouble merging the patch.  Patch.exe is only doing a partial job, so I am not sure what's wrong. It's as if the unified flag is not sticking. 
>>>>> 
>>>>>Could send me the complete affected files by any chance in a zip archive?
>>>>> 
>>>>>Thanks,
>>>>>Ved
>>>>>
>>>>>
>>>>>
>>>>>On Tuesday, January 14, 2014 5:06 AM, Robert Randall <rob...@gm...> wrote:
>>>>>  
>>>>>I apologize for not copying the list on this message.  Please review the patch below and let me know if you need another maintainer <grin>.  I've been developing Windows apps since before there was a Windows kernel <my age is showing>.
>>>>>>
>>>>>>
>>>>>>Best regards,
>>>>>>Robert
>>>>>>
>>>>>>
>>>>>>---------- Forwarded message ----------
>>>>>>From: Robert Randall <rob...@gm...>
>>>>>>Date: Mon, Jan 13, 2014 at 7:04 PM
>>>>>>Subject: Re: [Iometer-devel] a couple fixes, are the maintainers interested?
>>>>>>To: "lefferts, john" <joh...@em...>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Patch is below.  There are still a few issues I should clean up with regard to cleanly including the MFC headers.  I need to investigate one more internal bug report; loading .icf file with multiple managers results in the first manager being created other are not created. 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Index: src/GalileoApp.cpp
>>>>>>===================================================================
>>>>>>--- src/GalileoApp.cpp(revision 141) 
>>>>>>+++ src/GalileoApp.cpp(working copy)
>>>>>>@@ -122,6 +122,14 @@
>>>>>> delete login_port;
>>>>>> }
>>>>>>
>>>>>>+void CGalileoApp::CloseAllDocuments(BOOL bEndSession) 
>>>>>>+{
>>>>>>+if (bEndSession)
>>>>>>+   {
>>>>>>+      m_wndStatusBar.DestroyWindow();
>>>>>>+      m_wndToolBar.DestroyWindow();
>>>>>>+   }
>>>>>>+}
>>>>>> /////////////////////////////////////////////////////////////////////////////
>>>>>> // The one and only CGalileoApp object
>>>>>>
>>>>>>@@ -311,6 +319,8 @@
>>>>>> ///////////////////////////////////////////////////////////////////////////////
>>>>>> int CGalileoApp::ExitInstance()
>>>>>> {
>>>>>>+   manager_list.RemoveAllManagers(); 
>>>>>>+
>>>>>> delete[]m_pVersionString;
>>>>>> delete[]m_pVersionStringWithDebug;
>>>>>>
>>>>>>Index: src/GalileoApp.h 
>>>>>>===================================================================
>>>>>>--- src/GalileoApp.h(revision 141)
>>>>>>+++ src/GalileoApp.h(working copy) 
>>>>>>@@ -130,6 +130,7 @@
>>>>>> virtual int ExitInstance();
>>>>>> virtual BOOL OnIdle(LONG lCount);
>>>>>> virtual CDocument *OpenDocumentFile(LPCTSTR lpszFileName); 
>>>>>>+virtual void CloseAllDocuments(BOOL bEndSession); 
>>>>>> //}}AFX_VIRTUAL
>>>>>>
>>>>>> // Implementation 
>>>>>>Index: src/GalileoView.cpp
>>>>>>===================================================================
>>>>>>--- src/GalileoView.cpp(revision 141)
>>>>>>+++ src/GalileoView.cpp(working copy) 
>>>>>>@@ -1180,6 +1180,7 @@
>>>>>> void CGalileoView::OnFileOpen()
>>>>>> {
>>>>>> BOOL flags[NumICFFlags];
>>>>>>+CICFOpenDialog file_open_box;// open config file dialog box 
>>>>>>
>>>>>> // Show the custom file open dialog.
>>>>>> if (file_open_box.DoModal() == IDCANCEL)
>>>>>>@@ -1202,6 +1203,7 @@ 
>>>>>> void CGalileoView::OnFileSave()
>>>>>> {
>>>>>> BOOL flags[NumICFFlags];
>>>>>>+CICFSaveDialog file_save_box;// save config file dialog box 
>>>>>>
>>>>>> // Show the custom file save dialog.
>>>>>> if (file_save_box.DoModal() == IDCANCEL)
>>>>>>Index: src/GalileoView.h 
>>>>>>===================================================================
>>>>>>--- src/GalileoView.h(revision 141)
>>>>>>+++ src/GalileoView.h(working copy) 
>>>>>>@@ -182,8 +182,6 @@
>>>>>> CPropertySheet *m_pPropSheet;
>>>>>>
>>>>>>       protected:
>>>>>>-CICFOpenDialog file_open_box;// open config file dialog box 
>>>>>>-CICFSaveDialog file_save_box;// save config file dialog box
>>>>>>
>>>>>> // tracks whether parent frame has already been sized. 
>>>>>> BOOL m_bSizedBefore;
>>>>>>Index: src/ICFOpenDialog.cpp
>>>>>>===================================================================
>>>>>>--- src/ICFOpenDialog.cpp(revision 141) 
>>>>>>+++ src/ICFOpenDialog.cpp(working copy)
>>>>>>@@ -87,9 +87,10 @@
>>>>>>
>>>>>> ///////////////////////////////////////////////////////////////////////////// 
>>>>>> // CICFOpenDialog dialog
>>>>>>-    CICFOpenDialog::CICFOpenDialog()
>>>>>>-:  CFileDialog(TRUE, "icf", "", NULL,
>>>>>>-    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files (*.txt)|*.txt|All Files (*.*)|*.*||") 
>>>>>>+   CICFOpenDialog::CICFOpenDialog()
>>>>>>+:  CFileDialog(TRUE, "icf", NULL, OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT, 
>>>>>>+            "Iometer Configuration Files (*.icf)|*.icf|" "Text Files (*.txt)|*.txt|All Files (*.*)|*.*||",  
>>>>>>+               NULL, 0UL, FALSE)
>>>>>> {
>>>>>> CString title;
>>>>>> char *buf;
>>>>>>@@ -104,9 +105,6 @@ 
>>>>>> 
>>>>>> m_ofn.lpTemplateName = MAKEINTRESOURCE(IDD_FILEOPEN_OPTS);
>>>>>>
>>>>>>-// This is key to getting the templates working properly and secondary opens to work at all?! 
>>>>>>-m_bVistaStyle = FALSE;
>>>>>>-
>>>>>> //{{AFX_DATA_INIT(CICFOpenDialog) 
>>>>>> isCkTestSetup = TRUE;
>>>>>> isCkResultsDisplay = TRUE;
>>>>>>Index: src/ICFSaveDialog.cpp
>>>>>>=================================================================== 
>>>>>>--- src/ICFSaveDialog.cpp(revision 141)
>>>>>>+++ src/ICFSaveDialog.cpp(working copy)
>>>>>>@@ -88,8 +88,9 @@ 
>>>>>> /////////////////////////////////////////////////////////////////////////////
>>>>>> // CICFSaveDialog dialog
>>>>>>     CICFSaveDialog::CICFSaveDialog()
>>>>>>-:  CFileDialog(FALSE, "icf", "iometer", NULL, 
>>>>>>-    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files (*.txt)|*.txt|All Files (*.*)|*.*||")
>>>>>>+:  CFileDialog(FALSE, "icf", "iometer",  OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT, 
>>>>>>+    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files (*.txt)|*.txt|All Files (*.*)|*.*||",
>>>>>>+        NULL, 0UL, FALSE)
>>>>>> { 
>>>>>> CString title;
>>>>>> char *buf;
>>>>>>@@ -104,9 +105,6 @@
>>>>>>
>>>>>> m_ofn.lpTemplateName = MAKEINTRESOURCE(IDD_FILESAVE_OPTS); 
>>>>>>
>>>>>>-// This is key to getting the templates working properly and secondary opens to work at all?!
>>>>>>-m_bVistaStyle = FALSE; 
>>>>>>-
>>>>>> //{{AFX_DATA_INIT(CICFSaveDialog)
>>>>>> isCkTestSetup = TRUE;
>>>>>> isCkResultsDisplay = TRUE; 
>>>>>>Index: src/IOCommon.h
>>>>>>===================================================================
>>>>>>--- src/IOCommon.h(revision 141)
>>>>>>+++ src/IOCommon.h(working copy) 
>>>>>>@@ -204,17 +204,21 @@
>>>>>> #if defined(IOMTR_OSFAMILY_WINDOWS)   // Only first, because it is needed here!
>>>>>>  //#define VC_EXTRALEAN
>>>>>>  //#pragma warning (disable: 4242)
>>>>>>+#include "StdAfx.h" 
>>>>>>+//#define WIN32_LEAN_AND_MEAN 1
>>>>>>+//#include <Windows.h>
>>>>>>+//#include <windef.h>  
>>>>>>  #include <process.h>
>>>>>>  #include <io.h>
>>>>>>  #include <direct.h> 
>>>>>>- #include <afxwin.h>
>>>>>>- #include <afxext.h>
>>>>>>- #include <afxcmn.h>
>>>>>>- #include <winioctl.h>
>>>>>>+// #include <afxwin.h>
>>>>>>+// #include <afxext.h> 
>>>>>>+// #include <afxcmn.h>
>>>>>>  #include <iomanip>
>>>>>>  #include <winperf.h>
>>>>>>  #include <winreg.h>
>>>>>>- #include <afxmt.h>
>>>>>>+ #include <winioctl.h> 
>>>>>>+// #include <afxmt.h>
>>>>>>  #include <malloc.h>
>>>>>> #endif
>>>>>> // ----------------------------------------------------------------------------
>>>>>>@@ -868,7 +872,7 @@
>>>>>>  struct IOCQ {
>>>>>> CQ_Element      *element_list;
>>>>>> struct aiocb64 **aiocb_list;
>>>>>>-#ifdef IOMTR_SETTING_LINUX_LIBAIO 
>>>>>>+#ifdef IOMTR_SETTING_LINUX_LIBAIO
>>>>>> struct iocb **iocb_list;
>>>>>>         io_context_t io_ctx_id;
>>>>>>         struct io_event *events;
>>>>>>Index: src/IOPort.cpp 
>>>>>>===================================================================
>>>>>>--- src/IOPort.cpp(revision 141)
>>>>>>+++ src/IOPort.cpp(working copy) 
>>>>>>@@ -81,6 +81,7 @@
>>>>>> /* ######################################################################### */
>>>>>>
>>>>>> #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>>>>>>+#include "StdAfx.h" 
>>>>>> #include "GalileoApp.h"
>>>>>> #endif
>>>>>> #include "IOPort.h"
>>>>>>Index: src/IOPortTCP.cpp
>>>>>>===================================================================
>>>>>>--- src/IOPortTCP.cpp(revision 141)
>>>>>>+++ src/IOPortTCP.cpp(working copy)
>>>>>>@@ -89,7 +89,7 @@
>>>>>> /* ######################################################################### */ 
>>>>>>
>>>>>> #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>>>>>>-#include <afx.h>
>>>>>>+#include "StdAfx.h"
>>>>>> #endif
>>>>>>
>>>>>> #include "IOPortTCP.h" 
>>>>>>Index: src/IOTarget.cpp
>>>>>>===================================================================
>>>>>>--- src/IOTarget.cpp(revision 141)
>>>>>>+++ src/IOTarget.cpp(working copy) 
>>>>>>@@ -109,6 +109,9 @@
>>>>>> #if defined(IOMTR_OSFAMILY_UNIX) && defined(WORKAROUND_MOD_BUG)
>>>>>> return ((DWORDLONG)fmodl(spec.random = A * spec.random + B, limit)); 
>>>>>> #else
>>>>>>+#ifdef _DEBUG
>>>>>>+assert(limit > 0);
>>>>>>+#endif
>>>>>> return (spec.random = A * spec.random + B) % limit; 
>>>>>> #endif
>>>>>> }
>>>>>>Index: src/IOTargetDisk.cpp
>>>>>>===================================================================
>>>>>>--- src/IOTargetDisk.cpp(revision 141) 
>>>>>>+++ src/IOTargetDisk.cpp(working copy)
>>>>>>@@ -1329,10 +1329,14 @@
>>>>>> // Loop through the I/O queue looking for idle slots. 
>>>>>> for (i = 0; i < PREPARE_QDEPTH; i++) {
>>>>>> // Check to see if we've reached the end of the disk
>>>>>>-if (spec.disk_info.maximum_size &&
>>>>>>+// Windows debuggers lie when decoding spec.disk_info pushing 
>>>>>>+// values into local vars
>>>>>>+            int dd_sector_size = spec.disk_info.sector_size;
>>>>>>+            ULONGLONG dd_maximum_size = spec.disk_info.maximum_size; 
>>>>>>+            ULONGLONG dd_starting_sector = spec.disk_info.starting_sector;
>>>>>>+if (dd_maximum_size &&
>>>>>>     ((*prepare_offset + bytes) > 
>>>>>>-     ((spec.disk_info.starting_sector +
>>>>>>-       (DWORDLONG) spec.disk_info.maximum_size) * spec.disk_info.sector_size))) { 
>>>>>>+     ((dd_starting_sector + dd_maximum_size) * dd_sector_size))) {
>>>>>> // A maximum disk size was specified by the user, and the next write  
>>>>>> // would go past the specified maximum size.  
>>>>>> #ifdef _DEBUG
>>>>>>Index: src/IOTime.cpp
>>>>>>=================================================================== 
>>>>>>--- src/IOTime.cpp(revision 141)
>>>>>>+++ src/IOTime.cpp(working copy)
>>>>>>@@ -92,6 +92,9 @@
>>>>>> /* ##                                                                     ## */ 
>>>>>> /* ######################################################################### */
>>>>>>
>>>>>>+#if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>>>>>>+#include "StdAfx.h"
>>>>>>+#endif 
>>>>>> #include "IOCommon.h"
>>>>>>
>>>>>> #if defined(IOMTR_OS_LINUX)
>>>>>>Index: src/StdAfx.h
>>>>>>===================================================================
>>>>>>--- src/StdAfx.h(revision 141) 
>>>>>>+++ src/StdAfx.h(working copy)
>>>>>>@@ -58,11 +58,61 @@
>>>>>> /* ##                                                                     ## */
>>>>>> /* ######################################################################### */ 
>>>>>>
>>>>>>-#define VC_EXTRALEAN// Exclude rarely-used stuff from Windows headers
>>>>>>+//#define VC_EXTRALEAN// Exclude rarely-used stuff from Windows headers 
>>>>>>
>>>>>>-#include <afxwin.h>// MFC core and standard components
>>>>>>+//#include <afxwin.h>// MFC core and standard components 
>>>>>> //#include <afxext.h>         // MFC extensions
>>>>>>+//#ifndef _AFX_NO_AFXCMN_SUPPORT
>>>>>>+//#include <afxcmn.h>// MFC support for Windows Common Controls 
>>>>>>+//#endif// _AFX_NO_AFXCMN_SUPPORT
>>>>>>+//#include <afxtempl.h>
>>>>>>+
>>>>>>+// stdafx.h : include file for standard system include files, 
>>>>>>+// or project specific include files that are used frequently,
>>>>>>+// but are changed infrequently
>>>>>>+
>>>>>>+#pragma once
>>>>>>+
>>>>>>+#ifndef VC_EXTRALEAN
>>>>>>+#define VC_EXTRALEAN            // Exclude rarely-used stuff from Windows headers 
>>>>>>+#endif
>>>>>>+
>>>>>>+#include "targetver.h"
>>>>>>+
>>>>>>+//#define _AFX_NO_OLE_SUPPORT 1
>>>>>>+#define _ATL_CSTRING_EXPLICIT_CONSTRUCTORS      // some CString constructors will be explicit 
>>>>>>+
>>>>>>+// turns off MFC's hiding of some common and often safely ignored warning messages
>>>>>>+#define _AFX_ALL_WARNINGS
>>>>>>+
>>>>>>+#include <afxwin.h>         // MFC core and standard components 
>>>>>>+#include <afxext.h>         // MFC extensions
>>>>>>+
>>>>>>+#ifndef _AFX_NO_OLE_SUPPORT
>>>>>>+#include <afxdtctl.h>           // MFC support for Internet Explorer 4 Common Controls
>>>>>>+#endif
>>>>>> #ifndef _AFX_NO_AFXCMN_SUPPORT
>>>>>>-#include <afxcmn.h>// MFC support for Windows Common Controls
>>>>>>-#endif// _AFX_NO_AFXCMN_SUPPORT 
>>>>>>-//#include <afxtempl.h>
>>>>>>+#include <afxcmn.h>             // MFC support for Windows Common Controls
>>>>>>+#endif // _AFX_NO_AFXCMN_SUPPORT
>>>>>>+
>>>>>>+#include <afxcontrolbars.h>     // MFC support for ribbons and control bars 
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+
>>>>>>+#ifdef _UNICODE
>>>>>>+#if defined _M_IX86
>>>>>>+#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language='*'\"") 
>>>>>>+#elif defined _M_X64
>>>>>>+#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='amd64' publicKeyToken='6595b64144ccf1df' language='*'\"") 
>>>>>>+#else
>>>>>>+#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"") 
>>>>>>+#endif
>>>>>>+#endif
>>>>>>+
>>>>>>+
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>On Mon, Jan 13, 2014 at 3:10 PM, lefferts, john <joh...@em...> wrote:
>>>>>>
>>>>>>I appreciate you valuable efforts. 
>>>>>>>I think the developers would be better able to evaluate the technical merit of your changes if you take the extra time to construct a patch. 
>>>>>>>Even a simple diff stream would be useful for a review.
>>>>>>> 
>>>>>>>I have co-workers who complain about “crashes” when shutting-down a performance run—I wonder if you have addressed their issues. 
>>>>>>> 
>>>>>>>The SLN file under src/msvc9 says it was created with VS2008 (version 10) and I am using that. 
>>>>>>>It has the same constructor.
>>>>>>>  
>>>>>>>The developers have a comment that seems to indicate open-exclusive issues on reopen without prompt destruction of heap objects: 
>>>>>>> 
>>>>>>>      // This is key to getting the templates working properly and secondary opens to work at all?! 
>>>>>>>      m_bVistaStyle = FALSE;
>>>>>>>  
>>>>>>>I am interested in seeing your changes.
>>>>>>>  
>>>>>>> 
>>>>>>>From:Robert Randall [mailto:rob...@gm...] 
>>>>>>>Sent: Monday, January 13, 2014 3:44 PM
>>>>>>>To: iom...@li...
>>>>>>>Subject: Re: [Iometer-devel] a couple fixes, are the maintainers interested? 
>>>>>>> 
>>>>>>>I also fixed a problem when running in batch mode.  The destruction sequence of Windows causes an exception.  The cheap fix is implementing a function in CGalileoApp. 
>>>>>>> 
>>>>>>>Regards,
>>>>>>>Robert
>>>>>>>  
>>>>>>>On Mon, Jan 13, 2014 at 2:17 PM, Robert Randall <rob...@gm...> wrote:
>>>>>>> 
>>>>>>>Hello,
>>>>>>> 
>>>>>>>I've spent some time fixing a few simple problems with the latest version of MFC using the current trunk.  The CFileDialog constructors were being called incorrectly causing reference counting problems with COM.   The COM classes should not have been initialized in the first place.  Because the code was messing with m_bVistaStyle directly (not a good idea) it was causing the COM classes to be created but not destroyed which results in exceptions when running in the debugger and leaks resource when running a release build. 
>>>>>>> 
>>>>>>>I made these changes using VS 2012 and I don't have the tools to know if the CFileDialog constructor is compatible with previous releases of MFC.  I'm not sure how old a tool set is supported by the project when compiling on Windows.  Which versions of the compiler and MFC are supported? 
>>>>>>> 
>>>>>>>The constructor in the version of MFC I'm using is:
>>>>>>> 
>>>>>>>CFileDialog(
>>>>>>>   BOOL bOpenFileDialog, 
>>>>>>>   LPCTSTR lpszDefExt = NULL,
>>>>>>>   LPCTSTR lpszFileName = NULL,
>>>>>>>   DWORD dwFlags = OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT, 
>>>>>>>   LPCTSTR lpszFilter = NULL,
>>>>>>>   CWnd* pParentWnd = NULL,
>>>>>>>   DWORD dwSize = 0,
>>>>>>>   BOOL bVistaStyle = TRUE
>>>>>>>); 
>>>>>>> 
>>>>>>>I found one other minor problem.  When using a file on disk for testing the minimum Maximum Disk Size in sectors MUST be 128 or larger because of the code that IOTargetDisk::Prepare assumes that at least 64Kb will be written to the file.  A smaller value results in a divide by zero exception.  I'm not sure if Prepare should be fixed to handle smaller files or a minimum size should be enforced by the GUI.  Happy to make the fix either way. 
>>>>>>> 
>>>>>>> 
>>>>>>>Let me know if you would like a patch for these changes.
>>>>>>> 
>>>>>>>Best regards,
>>>>>>>Robert
>>>>>>>  
>>>>>>>-- 
>>>>>>>Robert Randall | rob...@gm...  
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 
>>>>>>>-- 
>>>>>>>Robert Randall | rob...@gm...  
>>>>>>
>>>>>>
>>>>>>
>>>>>>-- 
>>>>>>Robert Randall | rob...@gm...  
>>>>>>
>>>>>>
>>>>>>
>>>>>>-- 
>>>>>>Robert Randall | rob...@gm... 
>>>>>>
>>>>>>------------------------------------------------------------------------------
>>>>>>CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>>>>>Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>>>>>Critical Workloads, Development Environments & Everything In Between.
>>>>>>Get a Quote or Start a Free Trial Today. 
>>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>>>>>>_______________________________________________
>>>>>>Iometer-devel mailing list
>>>>>>Iom...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/iometer-devel
>>>>>>
>>>>>>
>>>>>>     
>>>>
>>>>
>>>>
>>>>-- 
>>>>Robert Randall | rob...@gm... 
>>>>
>>>>     
>>
>>
>>
>>-- 
>>Robert Randall | rob...@gm...  
>
>
>
>-- 
>Robert Randall | rob...@gm... 
>
>     

Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers interested?

[Robert R. <rob...@gm...>]

Hi Ved,

Did you get a chance to merge my changes into the SVN trunk?  Did you want
me to fix the multiple workers problem?

Best,
Robert


On Fri, Jan 17, 2014 at 7:24 AM, Robert Randall
<rob...@gm...>wrote:

> Hi Ved,
>
> Please let me know when you've committed the changes to the trunk of the
> repository so I may update my local copy.
>
> The problem is simple to reproduce.  Start IOMeter and create a
> configuration with two managers and save the configuration file.  Restart
> IOMeter and load the configuration file.  One manager will start
> automatically and IOmeter will wait for the second manager but it is never
> started.  If you would like me to fix this just let me know.
>
> If you would like me to join the maintainers of IOMeter I am happy to do
> so.  I'm an very interested in improving the marketplace perception of
> IOMeter.  It feels like updating the GUI and authoring documentation on how
> IOMeter performs the its IO under each OS implementation of Dynamo to
> better inform users of the capabilities and sophistication of the
> application might be quite helpful to improving the perception of IOMeter.
>
> We need an evangelist for IOMeter.  It is good stuff but it has suffered
> from a lack of attention and that is sad.  I've used it for longer than I
> care to admit for both network and storage performance testing.
>
> Best regards,
> Robert.
>
>
> On Thu, Jan 16, 2014 at 7:45 PM, Vedran Degoricija <ve...@ya...>wrote:
>
>> Hi Robert,
>>
>> Thank you. For the most part, it seems that the bVistaStyle piece
>> addresses the assert on exit under the debugger. Thanks for the catch!  I
>> also included most of your changes having to do stdafx cleanup.  Vistual
>> Studio analyzer also caught a couple of interesting deletes that were
>> missing the [] notation. I don't know if these would have been evident at
>> runtime.
>>
>> Lastly, you mentioned and issue with loading multiple workers. Can you
>> clarify that one please? I vaguely recall something about that, but it
>> would help me to have all of the info.
>>
>> Thanks,
>> Ved
>>
>>
>>   On Wednesday, January 15, 2014 6:13 AM, Robert Randall <
>> rob...@gm...> wrote:
>>
>> Hi Ved,
>>
>> Zip file of my source tree is attached.  Please feel free to ask
>> questions.
>>
>> BR,
>> Robert
>>
>>
>> On Wed, Jan 15, 2014 at 1:31 AM, Vedran Degoricija <ve...@ya...>wrote:
>>
>>  Hi Robert,
>>
>> (Apologies for calling you Randall earlier.)
>>
>> I am having trouble merging the patch.  Patch.exe is only doing a partial
>> job, so I am not sure what's wrong. It's as if the unified flag is not
>> sticking.
>>
>> Could send me the complete affected files by any chance in a zip archive?
>>
>> Thanks,
>> Ved
>>
>>
>>   On Tuesday, January 14, 2014 5:06 AM, Robert Randall <
>> rob...@gm...> wrote:
>>
>> I apologize for not copying the list on this message.  Please review the
>> patch below and let me know if you need another maintainer <grin>.  I've
>> been developing Windows apps since before there was a Windows kernel <my
>> age is showing>.
>>
>> Best regards,
>> Robert
>>
>> ---------- Forwarded message ----------
>> From: *Robert Randall* <rob...@gm...>
>> Date: Mon, Jan 13, 2014 at 7:04 PM
>> Subject: Re: [Iometer-devel] a couple fixes, are the maintainers
>> interested?
>> To: "lefferts, john" <joh...@em...>
>>
>>
>> Patch is below.  There are still a few issues I should clean up with
>> regard to cleanly including the MFC headers.  I need to investigate one
>> more internal bug report; loading .icf file with multiple managers results
>> in the first manager being created other are not created.
>>
>>
>> Index: src/GalileoApp.cpp
>> ===================================================================
>> --- src/GalileoApp.cpp (revision 141)
>> +++ src/GalileoApp.cpp (working copy)
>> @@ -122,6 +122,14 @@
>>   delete login_port;
>>  }
>>
>> +void CGalileoApp::CloseAllDocuments(BOOL bEndSession)
>> +{
>> + if (bEndSession)
>> +   {
>> +      m_wndStatusBar.DestroyWindow();
>> +      m_wndToolBar.DestroyWindow();
>> +   }
>> +}
>>
>>  /////////////////////////////////////////////////////////////////////////////
>>  // The one and only CGalileoApp object
>>
>> @@ -311,6 +319,8 @@
>>
>>  ///////////////////////////////////////////////////////////////////////////////
>>  int CGalileoApp::ExitInstance()
>>  {
>> +   manager_list.RemoveAllManagers();
>> +
>>   delete[]m_pVersionString;
>>   delete[]m_pVersionStringWithDebug;
>>
>> Index: src/GalileoApp.h
>> ===================================================================
>> --- src/GalileoApp.h (revision 141)
>> +++ src/GalileoApp.h (working copy)
>> @@ -130,6 +130,7 @@
>>   virtual int ExitInstance();
>>   virtual BOOL OnIdle(LONG lCount);
>>   virtual CDocument *OpenDocumentFile(LPCTSTR lpszFileName);
>> + virtual void CloseAllDocuments(BOOL bEndSession);
>>   //}}AFX_VIRTUAL
>>
>>  // Implementation
>> Index: src/GalileoView.cpp
>> ===================================================================
>> --- src/GalileoView.cpp (revision 141)
>> +++ src/GalileoView.cpp (working copy)
>> @@ -1180,6 +1180,7 @@
>>  void CGalileoView::OnFileOpen()
>>  {
>>   BOOL flags[NumICFFlags];
>> + CICFOpenDialog file_open_box; // open config file dialog box
>>
>>   // Show the custom file open dialog.
>>   if (file_open_box.DoModal() == IDCANCEL)
>> @@ -1202,6 +1203,7 @@
>>  void CGalileoView::OnFileSave()
>>  {
>>   BOOL flags[NumICFFlags];
>> + CICFSaveDialog file_save_box; // save config file dialog box
>>
>>   // Show the custom file save dialog.
>>   if (file_save_box.DoModal() == IDCANCEL)
>> Index: src/GalileoView.h
>> ===================================================================
>> --- src/GalileoView.h (revision 141)
>> +++ src/GalileoView.h (working copy)
>> @@ -182,8 +182,6 @@
>>   CPropertySheet *m_pPropSheet;
>>
>>        protected:
>> - CICFOpenDialog file_open_box; // open config file dialog box
>> - CICFSaveDialog file_save_box; // save config file dialog box
>>
>>   // tracks whether parent frame has already been sized.
>>   BOOL m_bSizedBefore;
>> Index: src/ICFOpenDialog.cpp
>> ===================================================================
>> --- src/ICFOpenDialog.cpp (revision 141)
>> +++ src/ICFOpenDialog.cpp (working copy)
>> @@ -87,9 +87,10 @@
>>
>>
>>  /////////////////////////////////////////////////////////////////////////////
>>  // CICFOpenDialog dialog
>> -    CICFOpenDialog::CICFOpenDialog()
>> -:  CFileDialog(TRUE, "icf", "", NULL,
>> -    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files
>> (*.txt)|*.txt|All Files (*.*)|*.*||")
>> +   CICFOpenDialog::CICFOpenDialog()
>> +:  CFileDialog(TRUE, "icf", NULL, OFN_HIDEREADONLY |
>> OFN_OVERWRITEPROMPT,
>> +            "Iometer Configuration Files (*.icf)|*.icf|" "Text Files
>> (*.txt)|*.txt|All Files (*.*)|*.*||",
>> +               NULL, 0UL, FALSE)
>>  {
>>   CString title;
>>   char *buf;
>> @@ -104,9 +105,6 @@
>>
>>   m_ofn.lpTemplateName = MAKEINTRESOURCE(IDD_FILEOPEN_OPTS);
>>
>> - // This is key to getting the templates working properly and secondary
>> opens to work at all?!
>> - m_bVistaStyle = FALSE;
>> -
>>   //{{AFX_DATA_INIT(CICFOpenDialog)
>>   isCkTestSetup = TRUE;
>>   isCkResultsDisplay = TRUE;
>> Index: src/ICFSaveDialog.cpp
>> ===================================================================
>> --- src/ICFSaveDialog.cpp (revision 141)
>> +++ src/ICFSaveDialog.cpp (working copy)
>> @@ -88,8 +88,9 @@
>>
>>  /////////////////////////////////////////////////////////////////////////////
>>  // CICFSaveDialog dialog
>>      CICFSaveDialog::CICFSaveDialog()
>> -:  CFileDialog(FALSE, "icf", "iometer", NULL,
>> -    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files
>> (*.txt)|*.txt|All Files (*.*)|*.*||")
>> +:  CFileDialog(FALSE, "icf", "iometer",  OFN_HIDEREADONLY |
>> OFN_OVERWRITEPROMPT,
>> +    "Iometer Configuration Files (*.icf)|*.icf|" "Text Files
>> (*.txt)|*.txt|All Files (*.*)|*.*||",
>> +        NULL, 0UL, FALSE)
>>  {
>>   CString title;
>>   char *buf;
>> @@ -104,9 +105,6 @@
>>
>>   m_ofn.lpTemplateName = MAKEINTRESOURCE(IDD_FILESAVE_OPTS);
>>
>> - // This is key to getting the templates working properly and secondary
>> opens to work at all?!
>> - m_bVistaStyle = FALSE;
>> -
>>   //{{AFX_DATA_INIT(CICFSaveDialog)
>>   isCkTestSetup = TRUE;
>>   isCkResultsDisplay = TRUE;
>> Index: src/IOCommon.h
>> ===================================================================
>> --- src/IOCommon.h (revision 141)
>> +++ src/IOCommon.h (working copy)
>> @@ -204,17 +204,21 @@
>>  #if defined(IOMTR_OSFAMILY_WINDOWS)   // Only first, because it is
>> needed here!
>>   //#define VC_EXTRALEAN
>>   //#pragma warning (disable: 4242)
>> +#include "StdAfx.h"
>> +//#define WIN32_LEAN_AND_MEAN 1
>> +//#include <Windows.h>
>> +//#include <windef.h>
>>   #include <process.h>
>>   #include <io.h>
>>   #include <direct.h>
>> - #include <afxwin.h>
>> - #include <afxext.h>
>> - #include <afxcmn.h>
>> - #include <winioctl.h>
>> +// #include <afxwin.h>
>> +// #include <afxext.h>
>> +// #include <afxcmn.h>
>>   #include <iomanip>
>>   #include <winperf.h>
>>   #include <winreg.h>
>> - #include <afxmt.h>
>> + #include <winioctl.h>
>> +// #include <afxmt.h>
>>   #include <malloc.h>
>>  #endif
>>  //
>> ----------------------------------------------------------------------------
>> @@ -868,7 +872,7 @@
>>   struct IOCQ {
>>   CQ_Element      *element_list;
>>   struct aiocb64 **aiocb_list;
>> -#ifdef IOMTR_SETTING_LINUX_LIBAIO
>> +#ifdef IOMTR_SETTING_LINUX_LIBAIO
>>   struct iocb **iocb_list;
>>          io_context_t io_ctx_id;
>>          struct io_event *events;
>> Index: src/IOPort.cpp
>> ===================================================================
>> --- src/IOPort.cpp (revision 141)
>> +++ src/IOPort.cpp (working copy)
>> @@ -81,6 +81,7 @@
>>  /*
>> ######################################################################### */
>>
>>  #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>> +#include "StdAfx.h"
>>  #include "GalileoApp.h"
>>  #endif
>>  #include "IOPort.h"
>> Index: src/IOPortTCP.cpp
>> ===================================================================
>> --- src/IOPortTCP.cpp (revision 141)
>> +++ src/IOPortTCP.cpp (working copy)
>> @@ -89,7 +89,7 @@
>>  /*
>> ######################################################################### */
>>
>>  #if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>> -#include <afx.h>
>> +#include "StdAfx.h"
>>  #endif
>>
>>  #include "IOPortTCP.h"
>> Index: src/IOTarget.cpp
>> ===================================================================
>> --- src/IOTarget.cpp (revision 141)
>> +++ src/IOTarget.cpp (working copy)
>> @@ -109,6 +109,9 @@
>>  #if defined(IOMTR_OSFAMILY_UNIX) && defined(WORKAROUND_MOD_BUG)
>>   return ((DWORDLONG)fmodl(spec.random = A * spec.random + B, limit));
>>  #else
>> +#ifdef _DEBUG
>> + assert(limit > 0);
>> +#endif
>>   return (spec.random = A * spec.random + B) % limit;
>>  #endif
>>  }
>> Index: src/IOTargetDisk.cpp
>> ===================================================================
>> --- src/IOTargetDisk.cpp (revision 141)
>> +++ src/IOTargetDisk.cpp (working copy)
>> @@ -1329,10 +1329,14 @@
>>   // Loop through the I/O queue looking for idle slots.
>>   for (i = 0; i < PREPARE_QDEPTH; i++) {
>>   // Check to see if we've reached the end of the disk
>> - if (spec.disk_info.maximum_size &&
>> + // Windows debuggers lie when decoding spec.disk_info pushing
>> + // values into local vars
>> +            int dd_sector_size = spec.disk_info.sector_size;
>> +            ULONGLONG dd_maximum_size = spec.disk_info.maximum_size;
>> +            ULONGLONG dd_starting_sector =
>> spec.disk_info.starting_sector;
>> + if (dd_maximum_size &&
>>      ((*prepare_offset + bytes) >
>> -     ((spec.disk_info.starting_sector +
>> -       (DWORDLONG) spec.disk_info.maximum_size) *
>> spec.disk_info.sector_size))) {
>> +     ((dd_starting_sector + dd_maximum_size) * dd_sector_size))) {
>>   // A maximum disk size was specified by the user, and the next write
>>   // would go past the specified maximum size.
>>  #ifdef _DEBUG
>> Index: src/IOTime.cpp
>> ===================================================================
>> --- src/IOTime.cpp (revision 141)
>> +++ src/IOTime.cpp (working copy)
>> @@ -92,6 +92,9 @@
>>  /* ##
>>   ## */
>>  /*
>> ######################################################################### */
>>
>> +#if defined(IOMTR_OS_WIN32) || defined(IOMTR_OS_WIN64)
>> +#include "StdAfx.h"
>> +#endif
>>  #include "IOCommon.h"
>>
>>  #if defined(IOMTR_OS_LINUX)
>> Index: src/StdAfx.h
>> ===================================================================
>> --- src/StdAfx.h (revision 141)
>> +++ src/StdAfx.h (working copy)
>> @@ -58,11 +58,61 @@
>>  /* ##
>>   ## */
>>  /*
>> ######################################################################### */
>>
>> -#define VC_EXTRALEAN // Exclude rarely-used stuff from Windows headers
>> +//#define VC_EXTRALEAN // Exclude rarely-used stuff from Windows headers
>>
>> -#include <afxwin.h> // MFC core and standard components
>> +//#include <afxwin.h> // MFC core and standard components
>>  //#include <afxext.h>         // MFC extensions
>> +//#ifndef _AFX_NO_AFXCMN_SUPPORT
>> +//#include <afxcmn.h> // MFC support for Windows Common Controls
>> +//#endif // _AFX_NO_AFXCMN_SUPPORT
>> +//#include <afxtempl.h>
>> +
>> +// stdafx.h : include file for standard system include files,
>> +// or project specific include files that are used frequently,
>> +// but are changed infrequently
>> +
>> +#pragma once
>> +
>> +#ifndef VC_EXTRALEAN
>> +#define VC_EXTRALEAN            // Exclude rarely-used stuff from
>> Windows headers
>> +#endif
>> +
>> +#include "targetver.h"
>> +
>> +//#define _AFX_NO_OLE_SUPPORT 1
>> +#define _ATL_CSTRING_EXPLICIT_CONSTRUCTORS      // some CString
>> constructors will be explicit
>> +
>> +// turns off MFC's hiding of some common and often safely ignored
>> warning messages
>> +#define _AFX_ALL_WARNINGS
>> +
>> +#include <afxwin.h>         // MFC core and standard components
>> +#include <afxext.h>         // MFC extensions
>> +
>> +#ifndef _AFX_NO_OLE_SUPPORT
>> +#include <afxdtctl.h>           // MFC support for Internet Explorer 4
>> Common Controls
>> +#endif
>>  #ifndef _AFX_NO_AFXCMN_SUPPORT
>> -#include <afxcmn.h> // MFC support for Windows Common Controls
>> -#endif // _AFX_NO_AFXCMN_SUPPORT
>> -//#include <afxtempl.h>
>> +#include <afxcmn.h>             // MFC support for Windows Common
>> Controls
>> +#endif // _AFX_NO_AFXCMN_SUPPORT
>> +
>> +#include <afxcontrolbars.h>     // MFC support for ribbons and control
>> bars
>> +
>> +
>> +
>> +
>> +
>> +
>> +
>> +
>> +
>> +#ifdef _UNICODE
>> +#if defined _M_IX86
>> +#pragma comment(linker,"/manifestdependency:\"type='win32'
>> name='Microsoft.Windows.Common-Controls' version='6.0.0.0'
>> processorArchitecture='x86' publicKeyToken='6595b64144ccf1df'
>> language='*'\"")
>> +#elif defined _M_X64
>> +#pragma comment(linker,"/manifestdependency:\"type='win32'
>> name='Microsoft.Windows.Common-Controls' version='6.0.0.0'
>> processorArchitecture='amd64' publicKeyToken='6595b64144ccf1df'
>> language='*'\"")
>> +#else
>> +#pragma comment(linker,"/manifestdependency:\"type='win32'
>> name='Microsoft.Windows.Common-Controls' version='6.0.0.0'
>> processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"")
>> +#endif
>> +#endif
>> +
>> +
>>
>>
>>
>> On Mon, Jan 13, 2014 at 3:10 PM, lefferts, john <joh...@em...>wrote:
>>
>> I appreciate you valuable efforts.
>> I think the developers would be better able to evaluate the technical
>> merit of your changes if you take the extra time to construct a patch.
>> Even a simple diff stream would be useful for a review.
>>
>> I have co-workers who complain about “crashes” when shutting-down a
>> performance run—I wonder if you have addressed their issues.
>>
>> The SLN file under src/msvc9 says it was created with VS2008 (version 10)
>> and I am using that.
>> It has the same constructor.
>>
>> The developers have a comment that seems to indicate open-exclusive
>> issues on reopen without prompt destruction of heap objects:
>>
>>       // This is key to getting the templates working properly and
>> secondary opens to work at all?!
>>       m_bVistaStyle = FALSE;
>>
>> I am interested in seeing your changes.
>>
>>
>> *From:* Robert Randall [mailto:rob...@gm...]
>> *Sent:* Monday, January 13, 2014 3:44 PM
>> *To:* iom...@li...
>> *Subject:* Re: [Iometer-devel] a couple fixes, are the maintainers
>> interested?
>>
>> I also fixed a problem when running in batch mode.  The destruction
>> sequence of Windows causes an exception.  The cheap fix is implementing a
>> function in CGalileoApp.
>>
>> Regards,
>> Robert
>>
>> On Mon, Jan 13, 2014 at 2:17 PM, Robert Randall <
>> rob...@gm...> wrote:
>>
>> Hello,
>>
>> I've spent some time fixing a few simple problems with the latest version
>> of MFC using the current trunk.  The CFileDialog constructors were being
>> called incorrectly causing reference counting problems with COM.   The COM
>> classes should not have been initialized in the first place.  Because the
>> code was messing with m_bVistaStyle directly (not a good idea) it was
>> causing the COM classes to be created but not destroyed which results in
>> exceptions when running in the debugger and leaks resource when running a
>> release build.
>>
>> I made these changes using VS 2012 and I don't have the tools to know if
>> the CFileDialog constructor is compatible with previous releases of MFC.
>>  I'm not sure how old a tool set is supported by the project when compiling
>> on Windows.  Which versions of the compiler and MFC are supported?
>>
>> The constructor in the version of MFC I'm using is:
>>
>>
>> CFileDialog(
>>
>>    BOOL bOpenFileDialog,
>>
>>    LPCTSTR lpszDefExt = NULL,
>>
>>    LPCTSTR lpszFileName = NULL,
>>
>>    DWORD dwFlags = OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT,
>>
>>    LPCTSTR lpszFilter = NULL,
>>
>>    CWnd* pParentWnd = NULL,
>>
>>    DWORD dwSize = 0,
>>
>>    BOOL bVistaStyle = TRUE
>>
>> );
>>
>>
>> I found one other minor problem.  When using a file on disk for testing
>> the minimum Maximum Disk Size in sectors MUST be 128 or larger because of
>> the code that IOTargetDisk::Prepare assumes that at least 64Kb will be
>> written to the file.  A smaller value results in a divide by zero
>> exception.  I'm not sure if Prepare should be fixed to handle smaller files
>> or a minimum size should be enforced by the GUI.  Happy to make the fix
>> either way.
>>
>>
>> Let me know if you would like a patch for these changes.
>>
>> Best regards,
>> Robert
>>
>> --
>> Robert Randall | rob...@gm...
>>
>>
>>
>> --
>> Robert Randall | rob...@gm...
>>
>>
>>
>>
>> --
>> Robert Randall | rob...@gm...
>>
>>
>>
>> --
>> Robert Randall | rob...@gm...
>>
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Iometer-devel mailing list
>> Iom...@li...
>> https://lists.sourceforge.net/lists/listinfo/iometer-devel
>>
>>
>>
>>
>>
>> --
>> Robert Randall | rob...@gm...
>>
>>
>>
>
>
> --
> Robert Randall | rob...@gm...
>



-- 
Robert Randall | rob...@gm...

Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers interested?

[Allen, W. <way...@in...>]

As Ved indicated we do have a defined test plan that we run against releases, so I too would be interested to know if there's a scenario where a change in performance reporting has been observed between releases using the same workload.

Best Regards,

Wayne

From: Vedran Degoricija [mailto:ve...@ya...]
Sent: Tuesday, January 14, 2014 10:24 PM
To: jo...@ei...; iom...@li...
Subject: Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers interested?

On performance degradation. I believe this was introduced with the data pattern generation feature. The current default setting (repeating bytes) does increase overheads, so selecting the pseudo random option gets you back to the original implementation. I don't recall what was the rationale behind not making the default match prior versions, but I am sure there was a good reason. :) And at the time, we did perform regression tests. So, if you still see issues with the pseudo random option, I'd like to know.

Thanks,
Ved

On Tuesday, January 14, 2014 5:42 PM, "jo...@ei...<mailto:jo...@ei...>" <jo...@ei...<mailto:jo...@ei...>> wrote:
As someone who hasn't been actively involved with iometer (or storage
benchmarking/testing) for a while I know that there are several
comments that I have heard over and over again.

1) Cross platform GUI - Daniel started looking at a java version
several years ago but never followed up.  I have had luck running
under wine in the past and was never interested in Mac.

2) performance degradation - The numbers that iometer was reporting
dropped off a little compared to previous versions. I was never able
to get hard numbers or revision numbers from anyone but this really
points out a need for automated regressions on known hardware with
multiple iometer versions.  I had these running in my lab for a while
back in 2000/2001, but my last intel contact moved on and I drifted
away and gave up my hardware empire ;-)

3) Tradeshow folks love the speedometer look, it is really one of the
defining features and if we did another GUI it should be replicated.

Thanks to all of those who have continued development and it is nice
to hear there are still people interested in helping out.

Joe

Quoting Robert Randall <rob...@gm...<mailto:rob...@gm...>>:

> So IOMeter is old and dead?  We automate our IOMeter runs exclusively so
> I'm not sure what mean by lack of automate-ability.  IOMeter can be
> executed from a command line without user intervention.  In that case it
> feels a bit unnecessary to display a GUI at all.  It might be nice if it
> had a 'silent' mode to avoid the painting overhead.
>
> BR,
> Robert
>
>
> On Tue, Jan 14, 2014 at 3:28 PM, Carl Zwanzig <cp...@co...<mailto:cp...@co...>> wrote:
>
>>  Hi,
>>
>>
>>
>> Maybe  8 months ago I tried linux fio vs windows fio and the numbers
>> tracked quite closely (same version of fio, on a dual-boot system). At this
>> point, we really only use iometer if it?s demanded, otherwise we?re using
>> fio, iozone, or filebench. iometer was a good tool, but has suffered from
>> very deferred maintenance. The lack of automate-ability doesn?t help,
>> either.
>>
>>
>>
>> z!
>>
>>
>>
>> *From:* Robert Randall [mailto:rob...@gm...<mailto:rob...@gm...>]
>> *Sent:* Tuesday, January 14, 2014 12:57 PM
>> *To:* Vedran Degoricija
>> *Cc:* iom...@li...<mailto:iom...@li...>
>> *Subject:* Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers
>> interested?
>>
>>
>>
>> FIO is all over the place.  The last time I reviewed their code they were
>> using the cygwin DLL as a shim for IO traffic (really bad idea).  The
>> latest versions use native calls.  I've not executed any 'bake off' number
>> in several months so I would have to collect some data and post it.
>>
>>
>>
>> Customers have informed me about the xperf vs. IOMeter discrepancies.  I
>> have not had time to collect independent data and confirm.  However, given
>> all of the changes introduced in Windows performance telemetry I don't find
>> this surprising.
>>
>> | rob...@gm...<mailto:rob...@gm...>
>>
>
>
>
> --
> Robert Randall | rob...@gm...<mailto:rob...@gm...>

>




------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Iometer-devel mailing list
Iom...@li...<mailto:Iom...@li...>
https://lists.sourceforge.net/lists/listinfo/iometer-devel

Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers interested?

[Vedran D. <ve...@ya...>]

On performance degradation. I believe this was introduced with the data pattern generation feature. The current default setting (repeating bytes) does increase overheads, so selecting the pseudo random option gets you back to the original implementation. I don't recall what was the rationale behind not making the default match prior versions, but I am sure there was a good reason. :) And at the time, we did perform regression tests. So, if you still see issues with the pseudo random option, I'd like to know.
 
Thanks,
Ved



On Tuesday, January 14, 2014 5:42 PM, "jo...@ei..." <jo...@ei...> wrote:
  
As someone who hasn't been actively involved with iometer (or storage  
>benchmarking/testing) for a while I know that there are several  
>comments that I have heard over and over again.
>
>1) Cross platform GUI - Daniel started looking at a java version  
>several years ago but never followed up.  I have had luck running  
>under wine in the past and was never interested in Mac.
>
>2) performance degradation - The numbers that iometer was reporting  
>dropped off a little compared to previous versions. I was never able  
>to get hard numbers or revision numbers from anyone but this really  
>points out a need for automated regressions on known hardware with  
>multiple iometer versions.  I had these running in my lab for a while  
>back in 2000/2001, but my last intel contact moved on and I drifted  
>away and gave up my hardware empire ;-)
>
>3) Tradeshow folks love the speedometer look, it is really one of the  
>defining features and if we did another GUI it should be replicated.
>
>Thanks to all of those who have continued development and it is nice  
>to hear there are still people interested in helping out.
>
>Joe
>
>
>
>Quoting Robert Randall <rob...@gm...>:
>
>> So IOMeter is old and dead?  We automate our IOMeter runs exclusively so
>> I'm not sure what mean by lack of automate-ability.  IOMeter can be
>> executed from a command line without user intervention.  In that case it
>> feels a bit unnecessary to display a GUI at all.  It might be nice if it
>> had a 'silent' mode to avoid the painting overhead.
>>
>> BR,
>> Robert
>>
>>
>> On Tue, Jan 14, 2014 at 3:28 PM, Carl Zwanzig <cp...@co...> wrote:
>>
>>>  Hi,
>>>
>>>
>>>
>>> Maybe  8 months ago I tried linux fio vs windows fio and the numbers
>>> tracked quite closely (same version of fio, on a dual-boot system). At this
>>> point, we really only use iometer if it?s demanded, otherwise we?re using
>>> fio, iozone, or filebench. iometer was a good tool, but has suffered from
>>> very deferred maintenance. The lack of automate-ability doesn?t help,
>>> either.
>>>
>>>
>>>
>>> z!
>>>
>>>
>>>
>>> *From:* Robert Randall [mailto:rob...@gm...]
>>> *Sent:* Tuesday, January 14, 2014 12:57 PM
>>> *To:* Vedran Degoricija
>>> *Cc:* iom...@li...
>>> *Subject:* Re: [Iometer-devel] Fwd: a couple fixes, are the maintainers
>>> interested?
>>>
>>>
>>>
>>> FIO is all over the place.  The last time I reviewed their code they were
>>> using the cygwin DLL as a shim for IO traffic (really bad idea).  The
>>> latest versions use native calls.  I've not executed any 'bake off' number
>>> in several months so I would have to collect some data and post it.
>>>
>>>
>>>
>>> Customers have informed me about the xperf vs. IOMeter discrepancies.  I
>>> have not had time to collect independent data and confirm.  However, given
>>> all of the changes introduced in Windows performance telemetry I don't find
>>> this surprising.
>>>
>>> | rob...@gm...
>>>
>>
>>
>>
>> --
>> Robert Randall | rob...@gm...
>>
>
>
>
>
>------------------------------------------------------------------------------
>CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>Learn Why More Businesses Are Choosing CenturyLink Cloud For
>Critical Workloads, Development Environments & Everything In Between.
>Get a Quote or Start a Free Trial Today. 
>http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>_______________________________________________
>Iometer-devel mailing list
>Iom...@li...
>https://lists.sourceforge.net/lists/listinfo/iometer-devel
>
>
>
>