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

sysfs: Export NVMe controller sysfs directory return function #801

Closed
wants to merge 1 commit into from

Conversation

ikegami-t
Copy link
Contributor

The path is returned with the controller name by the nvme scan. To return the path without the nvme scan nvme identify namespace.

The path is returned with the controller name by the nvme scan.
To return the path without the nvme scan nvme identify namespace.

Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
@igaw
Copy link
Collaborator

igaw commented Apr 9, 2024

I am not sure if we really need to do this. The sysfs is always mounted under /sys. The only reason the mount point is configurable in libnvme is for the unit tests. So we are able to run them against a sysfs mock.

Is there any good use case for nvme-cli for this, e.g. do you want to add also some unit tests for nvme-cli which would rely on a sysfs mock? For this purpose I'd say it could make sense.

So I tend to say no to this PR if we don't have a good use case why we should export it.

@ikegami-t
Copy link
Contributor Author

Okay I will do consider separately if the sysfs access functionality can be moved and combined from the nvme-cli to libnvme.

@ikegami-t ikegami-t closed this Apr 9, 2024
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

Successfully merging this pull request may close these issues.

2 participants