[nvmewin] Happy New Year... and status update

Wed Jan 20 13:11:24 PST 2016

Dell - Internal Use - Confidential
Dell would also prefer option 2.  We like to start with an "official" release that has been through some level of testing and has been WHQL'd and use that as our base.  If the official version passes all of our internal validation then we use that as our customer release, else we'll patch locally for our customer release and push the patches back upstream (fork and merge model).  This is what we've done for the prior few releases and the model seems to work well.
Thanks,
Austin

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Thomas Freeman
Sent: Wednesday, January 20, 2016 2:50 PM
To: Robles, Raymond C; suman.p at samsung.com; nvmewin-request at lists.openfabrics.org; nvmewin at lists.openfabrics.org
Cc: anshul at samsung.com; MANOJ THAPLIYAL; tru.nguyen at ssi.samsung.com
Subject: Re: [nvmewin] Happy New Year... and status update

Ray,
I don't have a strong opinion toward #3, I'm content with option #2 also.

Tom Freeman
Software Engineer, Device Manager and Driver Development
HGST, a Western Digital company
thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com>
507-322-2311

[cid:image001.png at 01D15394.D39900A0]
3605 Hwy 52 N
Rochester, MN 55901
www.hgst.com<https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/>

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org]<mailto:[mailto:nvmewin-bounces at lists.openfabrics.org]> On Behalf Of Robles, Raymond C
Sent: Wednesday, January 20, 2016 2:45 PM
To: suman.p at samsung.com<mailto:suman.p at samsung.com>; nvmewin-request at lists.openfabrics.org<mailto:nvmewin-request at lists.openfabrics.org>; nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Cc: anshul at samsung.com<mailto:anshul at samsung.com>; MANOJ THAPLIYAL <m.thapliyal at samsung.com<mailto:m.thapliyal at samsung.com>>; tru.nguyen at ssi.samsung.com<mailto:tru.nguyen at ssi.samsung.com>
Subject: Re: [nvmewin] Happy New Year... and status update

Hi Suman/Judy,

Thank you for your response. Right now, the current vote is...

Samsung - Option #2
HGST - Option #3
PMC Sierra - TBD

Alex/Kwok, what is your vote/preference on the release options below.

Thanks,
Ray

From: SUMAN PRAKASH B [mailto:suman.p at samsung.com]<mailto:[mailto:suman.p at samsung.com]>
Sent: Wednesday, January 20, 2016 9:10 AM
To: Robles, Raymond C; nvmewin-request at lists.openfabrics.org<mailto:nvmewin-request at lists.openfabrics.org>; nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Cc: tru.nguyen at ssi.samsung.com<mailto:tru.nguyen at ssi.samsung.com>; judy.brock at ssi.samsung.com<mailto:judy.brock at ssi.samsung.com>; MANOJ THAPLIYAL; anshul at samsung.com<mailto:anshul at samsung.com>
Subject: Re: Happy New Year... and status update

Hello Ray,

Samsung votes for Option #2. We push the remaining patches listed and then release in ~Q2 of 2015.

And as planned, Samsung will submit the following patches, along with some critical bug fixes.

a) Perf Opts (Samsung)
b) Win 8.1 Timers (Samsung)
c) EOL Read Only (Samsung)

And we will be ready with our first patch "Perf Opts" after 5 days of pushing the Namespace management patch to main branch.

Please let us know your opinion.

Regards,
Suman

----------------------------------------------------------------------

Message: 1
Date: Tue, 19 Jan 2016 14:32:45 +0000
From: Judy Brock-SSI <judy.brock at ssi.samsung.com<mailto:judy.brock at ssi.samsung.com>>
To: "Robles, Raymond C" <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>>,
 "'nvmewin at lists.openfabrics.org'" <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Subject: Re: [nvmewin] Happy New Year... and status update
Message-ID:
 <36E8D38D6B771A4BBDB1C0D800158A51865B7376 at SSIEXCH-MB3.ssi.samsung.com<mailto:36E8D38D6B771A4BBDB1C0D800158A51865B7376 at SSIEXCH-MB3.ssi.samsung.com>>
Content-Type: text/plain; charset="us-ascii"

Hi Ray,

We are still discussing internally. We will let you know which option we vote for soon!

Regards,
Judy

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C
Sent: Thursday, January 14, 2016 3:55 PM
To: 'nvmewin at lists.openfabrics.org'
Subject: [nvmewin] Happy New Year... and status update

Hello and Happy New Year,

I hope everyone had a great holiday season and is off to a great start to the new year!

As communicated last month, the patch from HGST for the SCSI multi-initiator changes has been approved and pushed. The holidays slowed down much of the progress on the OFA driver and there were several patches that did not get pushed prior to the end of the year. The list of patches remained to be pushed are as follows...

*         Namespace Management (Intel)

*         Perf Opts (Samsung)

*         Win 8.1 Timers (Samsung)

*         EOL Read Only (Samsung)

*         Concurrent channels (Google)

The namespace management patch will be sent out for review tomorrow (look for the patch email from Carolyn)... stay tuned!!!

However, once this patch is resolved, we as a community will have to make a decision on an official release strategy. The patch process and cadence was significantly slower in 2015 which leaves us with a few options.

1.       Release what is in the trunk today (or after the namespace management patch)... and call that the 2015 release (albeit later than expected)

2.       In lieu of an official 2015 release, we push the remaining patches listed above... and then release in ~Q2 of 2015. Basically skip a 2015 release and go right into the mid-2016 release.

3.       Remove the concept of "official releases" from the OFA Windows NVMe driver and just allow people, companies, and users to pull from the OFA trunk as necessary.

For #3 above, my thoughts are that because the OFA driver is not a production driver... but a reference and enabling driver, it should/could be managed as just that... a reference baseline driver that any potential user can go and grab the source, or contribute a patch. Nothing more... nothing less.

For the release decision, I'll be happy to call a meeting... but we can also handle it via email as well... just let me know. Feedback from all is welcome... but I would request mandatory feedback form the 4 reviewing companies: Samsung, HGST, PMC-Sierra, and Intel. How would you like to proceed?

Thanks,
Ray

[cid:image001.png at 01CB3870.4BB88E70]
Raymond C. Robles
Non-Volatile Memory Solutions Group
Intel Corporation
Office: 480-554-2600
Mobile: 480-399-0645

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/244aa8e7/attachment-0001.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/20160119/244aa8e7/attachment-0001.png>

------------------------------

Message: 2
Date: Tue, 19 Jan 2016 14:41:36 +0000
From: Thomas Freeman <thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com>>
To: "Robles, Raymond C" <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>>
Cc: "'nvmewin at lists.openfabrics.org'" <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Subject: Re: [nvmewin] Happy New Year... and status update
Message-ID:
 <BLUPR04MB6734B5581755C45230DDB33E9C10 at BLUPR04MB673.namprd04.prod.outlook.com<mailto:BLUPR04MB6734B5581755C45230DDB33E9C10 at BLUPR04MB673.namprd04.prod.outlook.com>>

Content-Type: text/plain; charset="us-ascii"

Thanks for the response Ray.
I'm fine with option 3.

Tom Freeman
Software Engineer, Device Manager and Driver Development
HGST, a Western Digital company
thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com%3cmailto:thomas.freeman at hgst.com>>
507-322-2311

[HGST_Logo_email]
3605 Hwy 52 N
Rochester, MN 55901
www.hgst.com<https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/<http://www.hgst.com%3chttps:/hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/>>

From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Friday, January 15, 2016 3:54 PM
To: Thomas Freeman <thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com>>
Cc: 'nvmewin at lists.openfabrics.org' <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Subject: RE: Happy New Year... and status update

Hi Tom,

Great questions... here are my thoughts. But I encourage others to chime in as well.

Is this purely a question of how the changes are packaged? [RCR] Exactly! I am merely making a suggestion that will ease the burden of having mandatory releases... as well as having to adhere to a schedule that really has no meaning to any particular product since the OFA driver is a reference driver. Much like the Linux community, any vendor can take our baseline and package it up as needed, but for the community itself, it just manages bug fix and feature patches as they come in.

Or do any of these options imply what type of fixes/changes will be delivered in the future? i.e. Does choosing option 3 imply that the driver is going into purely maintenance mode? [RCR] Not at all. Option 3 is simply us doing what we've done all along... with the exception of not doing any "official releases". All bug fix and feature patches would still be graciously accepted... and welcome :).

Or with that option, would there still be a coordinated effort to release new function along with fixes? [RCR] Exactly... see above responses.

Does this answer your questions Tom?

Thanks,
Ray

From: Thomas Freeman [mailto:thomas.freeman at hgst.com]
Sent: Friday, January 15, 2016 9:04 AM
To: Robles, Raymond C; 'nvmewin at lists.openfabrics.org'
Subject: RE: Happy New Year... and status update

Ray,
Is this purely a question of how the changes are packaged? Or do any of these options imply what type of fixes/changes will be delivered in the future? i.e. Does choosing option 3 imply that the driver is going into purely maintenance mode? Or with that option, would there still be a coordinated effort to release new function along with fixes?
Thanks,
Tom Freeman
Software Engineer, Device Manager and Driver Development
HGST, a Western Digital company
thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com%3cmailto:thomas.freeman at hgst.com>>
507-322-2311

[HGST_Logo_email]
3605 Hwy 52 N
Rochester, MN 55901
www.hgst.com<https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/<http://www.hgst.com%3chttps:/hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/>>

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org%3cmailto:nvmewin-bounces at lists.openfabrics.org>> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C
Sent: Thursday, January 14, 2016 5:55 PM
To: 'nvmewin at lists.openfabrics.org' <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org%3cmailto:nvmewin at lists.openfabrics.org>>>
Subject: [nvmewin] Happy New Year... and status update