* [SPDK] Cascade Lake SKU for SPDK dynamic threading
@ 2019-04-29 21:44 Young Tack Jin
0 siblings, 0 replies; 3+ messages in thread
From: Young Tack Jin @ 2019-04-29 21:44 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
Hi Ben and Darek,
Quick question on your presentation at the last SPDK Summit.
“Available on Cascade Lake N SKUs” on “Flexible and dynamic resource use
with SPDK”.
I’m confused as I found Y SKUs are supporting SST instead of N SKUs.
Please make sure which SKU is required for SPDK dynamic threading.
Thanks,
YT
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SPDK] Cascade Lake SKU for SPDK dynamic threading
@ 2019-04-30 14:27 Walker, Benjamin
0 siblings, 0 replies; 3+ messages in thread
From: Walker, Benjamin @ 2019-04-30 14:27 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Young Tack Jin
> Subject: [SPDK] Cascade Lake SKU for SPDK dynamic threading
>
> Hi Ben and Darek,
>
>
>
> Quick question on your presentation at the last SPDK Summit.
>
> “Available on Cascade Lake N SKUs” on “Flexible and dynamic resource use with
> SPDK”.
>
>
>
> I’m confused as I found Y SKUs are supporting SST instead of N SKUs.
I believe Y SKUs support SST-PP, but our talk was specifically talking about SST-BF and SST-CP which are only available on N SKUs. Looking on https://ark.intel.com seems to support this. (I'm just a lowly software developer though, so you should confirm with one of the Intel sales representatives).
>
> Please make sure which SKU is required for SPDK dynamic threading.
>
>
>
> Thanks,
>
> YT
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SPDK] Cascade Lake SKU for SPDK dynamic threading
@ 2019-04-30 15:26 Young Tack Jin
0 siblings, 0 replies; 3+ messages in thread
From: Young Tack Jin @ 2019-04-30 15:26 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
Hi Ben,
Thanks to point out sub features below SST. Right now I can't find out SKU
comparison table but it seems to distinguish PP, BF and CP.
Regards,
YT
-----Original Message-----
From: SPDK <spdk-bounces(a)lists.01.org> On Behalf Of Walker, Benjamin
Sent: Tuesday, April 30, 2019 7:27 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Cascade Lake SKU for SPDK dynamic threading
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Young Tack
> Jin
> Subject: [SPDK] Cascade Lake SKU for SPDK dynamic threading
>
> Hi Ben and Darek,
>
>
>
> Quick question on your presentation at the last SPDK Summit.
>
> “Available on Cascade Lake N SKUs” on “Flexible and dynamic resource
> use with SPDK”.
>
>
>
> I’m confused as I found Y SKUs are supporting SST instead of N SKUs.
I believe Y SKUs support SST-PP, but our talk was specifically talking about
SST-BF and SST-CP which are only available on N SKUs. Looking on
https://ark.intel.com seems to support this. (I'm just a lowly software
developer though, so you should confirm with one of the Intel sales
representatives).
>
> Please make sure which SKU is required for SPDK dynamic threading.
>
>
>
> Thanks,
>
> YT
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-04-30 15:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-04-29 21:44 [SPDK] Cascade Lake SKU for SPDK dynamic threading Young Tack Jin
-- strict thread matches above, loose matches on Subject: below --
2019-04-30 14:27 Walker, Benjamin
2019-04-30 15:26 Young Tack Jin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox