Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc/bluestore: add SPDK usage for bluestore #17654

Merged
merged 1 commit into from Sep 12, 2017

Conversation

Projects
None yet
2 participants
@yuyuyu101
Copy link
Member

commented Sep 11, 2017

Signed-off-by: Haomai Wang haomai@xsky.com

@yuyuyu101

This comment has been minimized.

Copy link
Member Author

commented Sep 11, 2017

that's why #17389 think db and wal not uses spdk. and lots of people get little benefits from spdk.
db and wal may locate at fs path if size specified.


If you want to use SPDK driver for NVME SSD, you need to specify NVMe serial
number here with "spdk:" prefix for ``bluestore_block_path``.
Users can use 'lspci -vvv -d 8086:0953 | grep "Device Serial Number"' to

This comment has been minimized.

Copy link
@liewegas

liewegas Sep 12, 2017

Member

For example, users can find the serial number with::

$ lspci -vvv -d 808... | grep ...

and then set::

bluestore block path = spdk:...

instance uses its own dpdk memory

In most cases, we only need one device to serve as data, db, db wal purposes.
We need to set configurations below to make sure all IOs issued under SPDK.::

This comment has been minimized.

Copy link
@liewegas

liewegas Sep 12, 2017

Member

I think thi si sonly needed for vstart, right? noramlly these default to empty, but vstart.sh sets them up (mostly just to exercise the code; not for a good reason)

This comment has been minimized.

Copy link
@yuyuyu101

yuyuyu101 Sep 12, 2017

Author Member

bluestore_block_wal_size default is not zero. let user make sure these configurations is ok.

This comment has been minimized.

Copy link
@liewegas

liewegas Sep 12, 2017

Member

but the _create options should be false, and those are only used by vstart for dev purposes. since spdk shouldn't be used with multiple devices it's probably simpler to leave that out to avoid confusion?

This comment has been minimized.

Copy link
@liewegas

liewegas Sep 12, 2017

Member

if we're worried about a vstart user having problems with spdk i'd rather disable wal/db for vstart to avoid it, and/or add an --spdk option to help

This comment has been minimized.

Copy link
@yuyuyu101

yuyuyu101 Sep 12, 2017

Author Member

hmm, let's remove _create options

@yuyuyu101 yuyuyu101 force-pushed the yuyuyu101:wip-spdk-doc branch from b25f407 to c922c06 Sep 12, 2017

doc/bluestore: add SPDK usage for bluestore
Signed-off-by: Haomai Wang <haomai@xsky.com>

@yuyuyu101 yuyuyu101 force-pushed the yuyuyu101:wip-spdk-doc branch from c922c06 to 537674b Sep 12, 2017

@liewegas liewegas merged commit 25ba984 into ceph:master Sep 12, 2017

5 checks passed

Docs: build check OK - docs built
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details
make check (arm64) make check succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.