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

About CLI support #32

Open
minwooim opened this issue Jul 21, 2019 · 4 comments
Open

About CLI support #32

minwooim opened this issue Jul 21, 2019 · 4 comments

Comments

@minwooim
Copy link

Hi LightNVM members,

I'd like to ask about a plan for the command line interfaces provided by
this library which is really awesome!

We have a plugin extension lnvm in nvme-cli for the OCSSD. But liblightnvm
also provides the command line interfaces so that it might have some
duplications or something to both of them. Maybe those two have different
goal of own purpose ;)

I'd like to kindly ask for a plan for this library here. Is lnvm extension not
going to be supported anymore in nvme-cli?

Thanks in advance :)
Minwoo Im

@safl
Copy link
Collaborator

safl commented Jul 21, 2019 via email

@MatiasBjorling
Copy link
Contributor

Hi Minwoo,

liblightnvm is often used to make it easy to use OCSSDs from user-space. Its cli tools allow easy translation from a generic address to the addresses of different OCSSDs (that have different geometries) and issuing basic I/O patterns.

liblightnvm could be extended to also call the same ioctls that nvme-cli uses to create targets in the kernel lightnvm subsystem. Although, that is what nvme-cli is currently used for.

I am not familiar with nvme-cli having the lnvm backend removed. Can you help me understand why that would be?

Kind regards,
Matias

@minwooim
Copy link
Author

@MatiasBjorling,

liblightnvm is often used to make it easy to use OCSSDs from user-space. Its cli tools allow easy translation from a generic address to the addresses of different OCSSDs (that have different geometries) and issuing basic I/O patterns.

liblightnvm could be extended to also call the same ioctls that nvme-cli uses to create targets in the kernel lightnvm subsystem. Although, that is what nvme-cli is currently used for.

I really appreciate your teaching here.

I am not familiar with nvme-cli having the lnvm backend removed. Can you help me understand why that would be?

I'm sorry if it sounded like lnvm extension should be removed. I don't think
that nvme-cli should remove the lnvm extension at all.

I just wanted to know the plan for those two different CLI interfaces'
responsibilities that I missed something here.

Thanks!

@minwooim
Copy link
Author

@safl ,

Hi Minwoo Im, Thanks for your interest. I am currently on vacation but let me get back to you during next week. Best, Simon søn.

I hope you enjoy your vacation :)
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants