[nvmewin] Iometer hang

Thu Jul 18 10:00:54 PDT 2013

Hi Judy,

See my comments in red...
________________________________

From: Judy Brock-SSI [mailto:judy.brock at ssi.samsung.com] 
Sent: Thursday, July 18, 2013 9:36 AM
To: Po-Yen Chang; Chang, Alex; Knoblaugh, Rick; Robles,Raymond C;
nvmewin at lists.openfabrics.org
Subject: RE: [nvmewin] Iometer hang

Hi Alex,

I'm still confused.

1.      I thought the suggested method for building for Windows Server
2012 (TRIM enabled) should be the same as for Windows 8 (TRIM enabled)
but that is not what it says below - there is no mention of building for
Windows Server 2012 w/TRIM enabled. 

Is it a mistake below or is it really the case that we are suggesting
that folks need to disable the TRIM code in the Server 2012 environment
as it says below? Because if we build for Server 2012 using either WDK
7600 build environment  or within VS 2012 when configured for Windows 7
in Project Property, we are disabling the TRIM code in that environment,
correct? 

I am so sure TRIM is supported in Server 2012. Could you please confirm
that? 

2.      When you say "I haven't got the chance to get to the bottom of
it and Yong from Huawei promised to find out more information from
Microsoft contacts he has.", get to the bottom of what?  Why are we
asking MS about an Iometer hang?  Unless perhaps it's the case that you
see this problem with Server 2012 (TRIM enabled) but not Windows 8 (TRIM
enabled)....is that the case? Please clarify why we think this is an OS
issue or why MS may have light to shed. 

      After tracing back the emails I exchanged with Rick (who
implemented the TRIM) for IOMeter issue, it was caused by mssing
COMPLETE_IN_DPC compiling flag when configuring project in VS 2012. Do
you specify that?

3.      Which versions of the OS did you see this problem on?  

Without specifying COMPLETE_IN_DPC, I've seen the IOMeter issue on
Windows 7 as well. 

4.      When I tried to debug the problem using a checked build version
of the driver, I got a whole different symptom. In fact that's when I
saw the crash which showed NVMe ISR interrupting NVMEStartIo critical
section due to lack of synchronization between the two paths. So while
it's good to have discovered that particular hole in the driver, I was
unable to debug the Iometer hang because it only manifested with the
free build driver binary.  Does anyone know how to configure the build
to generate free build symbols? It won't be as painless but I could
debug the free build with the help of a symbol file at least - and maybe
a mixed assembly/source listing and a map file... 

See my comments on #2. 

Thanks,

Judy

From: Po-Yen Chang [mailto:PoYen.Chang at pmcs.com] 
Sent: Thursday, July 18, 2013 9:19 AM
To: Judy Brock-SSI; Chang, Alex; Knoblaugh, Rick; Robles,Raymond C;
nvmewin at lists.openfabrics.org
Subject: RE: [nvmewin] Iometer hang

Judy,

No, I haven't got the chance to get to the bottom of it and Yong from
Huawei promised to find out more information from Microsoft contacts he
has.

Here are the suggested methods to build the binary for different
Operating Systems:

For Windows 7, Server 2008 R2, Server 2012, Windows 8 (TRIM disabled):

Within WDK 7600 build environment, or

Within VS 2012 when configured for Windows 7 in Project Property.

For Windows 8 (TRIM enabled):

Within VS 2012 when configured for Windows 8 in Project Property.

Thanks,
Alex

________________________________

From: Judy Brock-SSI [mailto:judy.brock at ssi.samsung.com] 
Sent: Thursday, July 18, 2013 9:01 AM
To: Po-Yen Chang; Chang, Alex; Knoblaugh, Rick; Robles,Raymond C; 
nvmewin at lists.openfabrics.org
Subject: RE: [nvmewin] Iometer hang

I ran on Windows Server 2012 and the binary (not built by me) was built
with VS 2012/Win 8 WDK. 

Can you explain what you mean by compatibility issues? Did you isolate
the root cause of the hang?

Thanks,

Judy

From: Po-Yen Chang [mailto:PoYen.Chang at pmcs.com] 
Sent: Thursday, July 18, 2013 8:57 AM
To: Judy Brock-SSI; Chang, Alex; Knoblaugh, Rick; Robles,Raymond C; 
nvmewin at lists.openfabrics.org
Subject: RE: [nvmewin] Iometer hang

Hi Judy,

Could you please let me know how you built the binary and which
operating system you ran on? There are some compatibility issue here and
that's why we need to release separate binary package for Windows 8,
where TRIM is enabled.

Thanks,

Alex

________________________________

From: nvmewin-bounces at lists.openfabrics.org [
mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Judy
Brock-SSI
Sent: Thursday, July 18, 2013 12:33 AM
To: Chang, Alex; Knoblaugh, Rick; Robles,Raymond C; 
nvmewin at lists.openfabrics.org
Subject: [nvmewin] Iometer hang

Alex,

We are seeing the same problem you describe below with IOMeter stopping
right after hitting "Start Tests" with 4k sequential writes.  To be
fair, I haven't tried top of repository tree, I was using
TRIM_command_support label revision 72. Did you ever find out what
caused this problem?

Thanks,

Judy

From: nvmewin-bounces at lists.openfabrics.org [
mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Chang, Alex
Sent: Thursday, June 13, 2013 9:40 AM
To: Knoblaugh, Rick; Robles, Raymond C; nvmewin at lists.openfabrics.org
Subject: Re: [nvmewin] LSI Trim Patch

Hi Rick,

I did some basic tests like disk formats, SCSICompliance, SDStress and
IOMeter. They're all working fine except IOMeter, which I configured as
4Kbyte, sequential writes. IOMeter stops right after hitting "Start
Tests" (green flag). Do you see the problem when you tested it?

Thanks,
Alex

________________________________

From: nvmewin-bounces at lists.openfabrics.org [
mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Knoblaugh,
Rick
Sent: Friday, June 07, 2013 6:38 PM
To: Robles, Raymond C; nvmewin at lists.openfabrics.org
Subject: [nvmewin] ***UNCHECKED*** LSI Trim Patch

Hi Ray,

               Per your request, since we will switch order, moving
Intel patch to the number 3 position, I'm sending LSI's Trim patch. 

Password for the attached file is: lsi1234. Also, I have attached a
document here that describes what was changed/added. 

              It would be great if everyone can review and please let me
know any feedback.

Thanks.

       -Rick

From: Robles, Raymond C [mailto:raymond.c.robles at intel.com] 
Sent: Monday, June 03, 2013 5:12 PM
To: Knoblaugh, Rick; nvmewin at lists.openfabrics.org
Subject: RE: Sandisk patch delay

Hi Rick,

That's great news! LSI will be 3rd in line after IDT and Intel.  Thanks
for the contributions to TRIM.

Thanks,

Ray

From: Knoblaugh, Rick [mailto:Rick.Knoblaugh at lsi.com] 
Sent: Monday, June 03, 2013 4:57 PM
To: Robles, Raymond C; nvmewin at lists.openfabrics.org
Subject: RE: Sandisk patch delay

Hi Ray,

                    We also have the patch for Trim. It is ready to
send. Please let me know when you would like me to send out.

Thanks,

                 -Rick

From: nvmewin-bounces at lists.openfabrics.org [
mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles,
Raymond C
Sent: Monday, June 03, 2013 4:44 PM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] Sandisk patch delay

Hello,

It appears the Sandisk patch for Mode Sense is taking longer than
expected. In order to keep things moving along with the OFA driver, I'm
going to take the Sandisk patch offline for now until they can resolve
their issues.  Once they have worked out the kinks, they can re-submit.
In the meantime, Alex from IDT has a patch he'd like to push and I also
have a patch I'd like to push.

Alex, please send your patch out for code review as soon as possible and
then I will send out my patch immediately after.

Thanks,

Ray

Raymond C. Robles

NVM Solutions Group | Internal SSD Engineering

Technology & Manufacturing Group

Intel Corporation

Desk: 480.554.2600

Mobile: 480.399.0645

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20130718/4fc42864/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1756 bytes
Desc: image001.png
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20130718/4fc42864/attachment.png>