-
Notifications
You must be signed in to change notification settings - Fork 697
plugin/ocp_get_feature_fid_c8h:Added the OCP Get Feature FID=C8h comm… #2788
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
plugin/ocp_get_feature_fid_c8h:Added the OCP Get Feature FID=C8h comm… #2788
Conversation
ikegami-t
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Is the
namespace-idoption really required? Since it looks the `nvme get-feature' command can be used for the testing purpose. - For the commit message seems needed to be followed the following guide line.
https://docs.kernel.org/process/submitting-patches.html#subject-line
| opts+=" --comp-id= -i --list -l --verbose -v \ | ||
| --output-format -o --timeout= -t" | ||
| ;; | ||
| "get-latency-monitor") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This command not related to the PR changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ikegami-t - Incorporated the review comments
|
|
||
| err = nvme_get_features(&args); | ||
| if (!err) { | ||
| printf("get-feature:0xC8 %s value: %#08x\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add support for human-readable and json print outputs? (I think it is okay to be done in future separately.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ikegami-t - Printing the libnvme api return value. I am thinking json format is not required
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| } | ||
|
|
||
| static int ocp_get_telemetry_profile_feature(int argc, char **argv, struct command *cmd, | ||
| struct plugin *plugin) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation error should be fixed as below. (5 tab spaces and 5 white spaces needed before struct plugin *plugin)
static int ocp_get_telemetry_profile_feature(int argc, char **argv, struct command *cmd,
- struct plugin *plugin)
+ struct plugin *plugin)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ikegami-t - Incorporated the review comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks not changed the indentation error part.
|
Besides addressing @ikegami-t comment, a rebase is necessary. Thanks. |
415e7b5 to
aa4d473
Compare
@ikegami-t - We have added the get feature FID=C8h command api to test the command with various NSID value and also ocp-nvme.c library should have set feature and get feature command api for all the FIDs |
@igaw - Resolved the conflict issue. |
Yes I see but the command added will not be used actually I think. |
|
What is the status here? Is it ready to be merged or are there open question/request? |
|
I am not really deep into the OCP spec, so I can't really comment if this is usual or not. At least for Samsung it seems useful. Do you have a suggestion how to move forward? FWIW, we have also added stuff from the nvme spec which doesn't really seem useful but still we have it in the nvme-cli. I'd say as long the code fits into the exiting code base and doesn't impose long time maintainability issues we should accept it. |
|
@igaw Thanks for your comment. Yes agreed for now and just |
|
Regarding your PR:` #596 The reason why this was not accepted is that this particular command really messes with the transport layer a lot and thus userspace shouldn't really touch these bits. If you really want to add it, we could hide it behind something 'do you really want to do this?' as we have for the format command. Of course there are more such low level commands which could get the transport out of sync and as you said, it's possible to it with the Okay, I'll going to merge this now. I understand this one is more like a plumbing command. |
Enabled Get Feature command (FID=C8h) api with sel, namespace-id, no-uuid command line arguments. namespace-id added to the test the command with active, inactive and invalid nsid values. Reviewed-by: Karthik Balan <[email protected]> Reviewed-by: Arunpandian J <[email protected]> Signed-off-by: Vigneshwaran Saravanan <[email protected]>
aa4d473 to
d421e85
Compare
|
Thanks! |
|
Thanks for your explanation. I could unserstand well. |

…and api
Enabled Get Feature command (FID=C8h) api with sel, namespace-id, no-uuid command line arguments. namespace-id added to the test the command with active, inactive and invalid nsid values.
Reviewed-by: Karthik Balan [email protected]
Reviewed-by: Arunpandian J [email protected]