* Re: [SPDK] Blob store
@ 2017-06-30 16:13 Walker, Benjamin
0 siblings, 0 replies; 3+ messages in thread
From: Walker, Benjamin @ 2017-06-30 16:13 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Thu, 2017-06-15 at 09:16 -0700, tejasgole wrote:
> Hi,
>
> Is there any example code for blob store to use nvme device directly without
> the block dev layer?
>
> If not, is there even a document on the order in which APIs need to be invoked
> to set this up correctly?
>
> The way I have it setup, spdk_bs_init () followed by spdk_bs_md_create_blob ()
> both succeed, but spdk_bs_md_open_blob () spins forever.
>
> It keeps issuing reads to lba=3.
I haven't written an example for how to do this yet. Are you able to test the
blob store using the bdev layer like in the rest of the examples for now? I
think that will be a lot more straightforward, but if there are concerns about
the bdev layer I'd love to understand what those are.
>
> Thanks
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [SPDK] Blob store
@ 2017-06-30 16:29 tejasgole
0 siblings, 0 replies; 3+ messages in thread
From: tejasgole @ 2017-06-30 16:29 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
I got past the issue. The issue was blob store block size (4K) was mismatched with the nvme device (512b). Once I converted correctly, everything worked.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: "Walker, Benjamin" <benjamin.walker(a)intel.com> Date: 6/30/17 9:13 AM (GMT-08:00) To: spdk(a)lists.01.org Subject: Re: [SPDK] Blob store
On Thu, 2017-06-15 at 09:16 -0700, tejasgole wrote:
> Hi,
>
> Is there any example code for blob store to use nvme device directly without
> the block dev layer?
>
> If not, is there even a document on the order in which APIs need to be invoked
> to set this up correctly?
>
> The way I have it setup, spdk_bs_init () followed by spdk_bs_md_create_blob ()
> both succeed, but spdk_bs_md_open_blob () spins forever.
>
> It keeps issuing reads to lba=3.
I haven't written an example for how to do this yet. Are you able to test the
blob store using the bdev layer like in the rest of the examples for now? I
think that will be a lot more straightforward, but if there are concerns about
the bdev layer I'd love to understand what those are.
>
> Thanks
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1876 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* [SPDK] Blob store
@ 2017-06-15 16:16 tejasgole
0 siblings, 0 replies; 3+ messages in thread
From: tejasgole @ 2017-06-15 16:16 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Hi,
Is there any example code for blob store to use nvme device directly without the block dev layer?
If not, is there even a document on the order in which APIs need to be invoked to set this up correctly?
The way I have it setup, spdk_bs_init () followed by spdk_bs_md_create_blob () both succeed, but spdk_bs_md_open_blob () spins forever.
It keeps issuing reads to lba=3.
Thanks
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 663 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-06-30 16:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-06-30 16:13 [SPDK] Blob store Walker, Benjamin
-- strict thread matches above, loose matches on Subject: below --
2017-06-30 16:29 tejasgole
2017-06-15 16:16 tejasgole
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox