Open minwooim opened 5 years ago
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. 21. jul. 2019 13.42 skrev Minwoo Im notifications@github.com:
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
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OpenChannelSSD/liblightnvm/issues/32?email_source=notifications&email_token=AAEUTEPWMYGFPQ2ZIGHUATLQARDTLA5CNFSM4IFR7PQKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAPNJ5A, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEUTEOSNRUBKF23KY47723QARDTLANCNFSM4IFR7PQA .
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
@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!
@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!
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