You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, we have an empty backend_nvme_pcie.proto and backend_nvme_tcp.proto. However, it is planned to have fabrics and pcie in one backend service. Probably, rename of backend_nvme_tcp.proto to backend_nvme.proto and deletion of backend_nvme_pcie.proto makes sense.
Also, since we can connect to local pcie nvme drives by the service in backend_nvme_tcp.proto it might make sense to rename messages: NvmeRemoteController* -> NvmeBackendController* NvmeRemoteNamespace* -> NvmeBackendNamespace*
glimchb
changed the title
Make storage backend nvme file and content consistent with provided services
[storage] NvmeRemoteController* -> NvmeBackendController*
Oct 24, 2023
At the moment, we have an empty backend_nvme_pcie.proto and backend_nvme_tcp.proto. However, it is planned to have fabrics and pcie in one backend service. Probably, rename of
backend_nvme_tcp.proto
tobackend_nvme.proto
and deletion ofbackend_nvme_pcie.proto
makes sense.Also, since we can connect to local pcie nvme drives by the service in
backend_nvme_tcp.proto
it might make sense to rename messages:NvmeRemoteController*
->NvmeBackendController*
NvmeRemoteNamespace*
->NvmeBackendNamespace*
Additionally, see #343
The text was updated successfully, but these errors were encountered: