From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Content for v18.10.x
Date: Thu, 13 Dec 2018 14:26:03 +0000 [thread overview]
Message-ID: <A183EE43-C38C-4034-86B0-FFE0435969BB@intel.com> (raw)
In-Reply-To: 94ec5e4f-a856-3a65-b97b-19b1cbb48411@dev.mellanox.co.il
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
On 12/12/18, 9:29 PM, "SPDK on behalf of Sasha Kotchubievsky" <spdk-bounces(a)lists.01.org on behalf of sashakot(a)dev.mellanox.co.il> wrote:
Hi Tomek,
Great news
Can you confirm that 2M page issue in NVME-OF RDMA is fixed in 18.10.1?
It was fixed by https://github.com/spdk/spdk/commit/7a58660 , which is
not in the 18.10.X . But, maybe it's fixed by other patches that are in.
If you need some help to reproduce and retest the issue, let me know.
I'd consider to merge following patches into 18.10.1:
- https://review.gerrithub.io/c/spdk/spdk/+/436974 - This patch
fixes resource leakage
- https://review.gerrithub.io/c/spdk/spdk/+/436887 improves error
handling
- https://review.gerrithub.io/c/spdk/spdk/+/430802 - This patch fixes
tests compilation on ARM platform. It's pretty annoying issue.
FYI - I've merged 430802 just now, and cherry picked it onto the v18.10.x branch here:
https://review.gerrithub.io/#/c/spdk/spdk/+/437054/
Thanks
Sasha
On 12/12/2018 10:17 PM, Zawadzki, Tomasz wrote:
> Hi Sasha,
>
> Yes, there is an update to SPDK 18.10.1 coming that focuses on adding packaging for SPDK, along with important fixes that were merged since last release.
>
> Most of the patches were cherry-picked and merged into 18.10.x branch. Currently finishing up couple of the last ones.
> The plan is to release it by end of this week.
>
> Thanks,
> Tomek
>
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Sasha Kotchubievsky
> Sent: Wednesday, December 12, 2018 11:02 AM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] Content for v18.10.x
>
> Hi,
>
> As I see, some patches from "master" are merged into v18.10.x branch.
>
> https://github.com/spdk/spdk/tree/v18.10.x
>
> Are there plans to update v18.10 released in October?
>
>
> Best regards
>
> Sasha
>
>
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2018-12-13 14:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 14:26 Harris, James R [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-19 21:36 [SPDK] Content for v18.10.x Walker, Benjamin
2018-12-19 18:11 Sasha Kotchubievsky
2018-12-19 17:25 Lance Hartmann ORACLE
2018-12-19 17:09 Walker, Benjamin
2018-12-17 18:37 Walker, Benjamin
2018-12-17 18:32 Sasha Kotchubievsky
2018-12-17 15:36 Harris, James R
2018-12-16 11:30 Sasha Kotchubievsky
2018-12-14 16:21 Harris, James R
2018-12-13 15:13 Sasha Kotchubievsky
2018-12-13 7:45 Sasha Kotchubievsky
2018-12-13 5:11 Zawadzki, Tomasz
2018-12-13 4:29 Sasha Kotchubievsky
2018-12-12 20:17 Zawadzki, Tomasz
2018-12-12 19:01 Sasha Kotchubievsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A183EE43-C38C-4034-86B0-FFE0435969BB@intel.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox