<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
On Jan 6, 2020, at 17:02, James Simmons <<a href="mailto:jsimmons@infradead.org" class="">jsimmons@infradead.org</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">Hi all,<br class="">
At the LUG in Houston, I said that I hoped to submit something upstream<br class="">
by the end of 2019. Clearly that isn't going to happen now.<br class="">
<br class="">
The main reason that caused me to not even try is IPv6 support.<br class="">
It became apparent to me that LNet would not be accepted until it has<br class="">
working IPv6 support, and that doesn't exist yet.<br class="">
I hope to put some development time into IPv6, and to have something<br class="">
that works and is worth reviewing by the end of January 2020.<br class="">
</blockquote>
<br class="">
That would be awesome. I believe the original plan was for IPv6 support<br class="">
for 2.14 but USDP didn't make it in for 2.13 so everything got delayed.<br class="">
<br class="">
<blockquote type="cite" class="">The other issue is that development has progressed slowly because<br class="">
there is no spare review bandwidth. James has contributed a lot, and<br class="">
others have helped, but reviewing patches for two code streams (OpenSFS<br class="">
and Linux-upstream) turns out to be too much to ask for.<br class="">
So I've decided to take a different approach. From now on I'm not<br class="">
going to wait for reviews for patches going into my linux-lustre tree.<br class="">
Part of my justification for this is that historically, review hasn't<br class="">
really provided much promise of correctness. Patches go missing.<br class="">
Random lines from patches go missing. Errors creep in in other ways.<br class="">
</blockquote>
<br class="">
I have been going over the patches from your backport tree to find<br class="">
missing patches and test for regressions. I think all regressions I<br class="">
saw was stomped out for everything for 2.12. I'm doing full regression<br class="">
right now. The only bug I see now is very unique to the linux client.<br class="">
</div>
</div>
</blockquote>
<div class="">
<div class=""><br class="">
</div>
</div>
<div class="">
<div class="">[snip]<br class="">
</div>
</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">I also have started working through the 2.13 release. I'm up to 2.12.54<br class="">
but no heavy testing as of yet of those patches. Once I'm done testing<br class="">
2.12 in depth I can push quickly through 2.13 and even sync up to<br class="">
OpenSFS branch. I think the back porting work can be wrapped up by the<br class="">
end of the month.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
I thought the goal was to stop at 2.12.x (following the b2_12 branch to get</div>
<div>important fixes) and try to get that included upstream? That gives a good</div>
<div>point-in-time to track, and ensures that the upstream code is aligned with</div>
<div>a relatively stable version of the code. It also has the major benefit that</div>
<div>2.12 is an LTS branch and we will need to keep compatibility with that for</div>
<div>a long time, which isn't always true of intermediate releases.</div>
<div><br class="">
</div>
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div>Cheers, Andreas</div>
<div>--</div>
<div>Andreas Dilger</div>
<div>Principal Lustre Architect</div>
<div>Whamcloud</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<br class="">
</body>
</html>