Seperate Metadata Support
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We are working on NVMe driver in linux kernel 4.13.10. We want to test an NVMe I/O commands with separate metadata. We send the command using IOCTL, and along the command we send the buffer to be used by driver to be sent to controller for metadata. The driver uses blk_execute_rq to submit the command to the block layer.
This implementation works properly for normal commands, but when used with separate metadata, it crashes at blk_mq_start_request.
Any help or information regarding this would be useful.
linux-kernel
New contributor
add a comment |Â
up vote
0
down vote
favorite
We are working on NVMe driver in linux kernel 4.13.10. We want to test an NVMe I/O commands with separate metadata. We send the command using IOCTL, and along the command we send the buffer to be used by driver to be sent to controller for metadata. The driver uses blk_execute_rq to submit the command to the block layer.
This implementation works properly for normal commands, but when used with separate metadata, it crashes at blk_mq_start_request.
Any help or information regarding this would be useful.
linux-kernel
New contributor
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are working on NVMe driver in linux kernel 4.13.10. We want to test an NVMe I/O commands with separate metadata. We send the command using IOCTL, and along the command we send the buffer to be used by driver to be sent to controller for metadata. The driver uses blk_execute_rq to submit the command to the block layer.
This implementation works properly for normal commands, but when used with separate metadata, it crashes at blk_mq_start_request.
Any help or information regarding this would be useful.
linux-kernel
New contributor
We are working on NVMe driver in linux kernel 4.13.10. We want to test an NVMe I/O commands with separate metadata. We send the command using IOCTL, and along the command we send the buffer to be used by driver to be sent to controller for metadata. The driver uses blk_execute_rq to submit the command to the block layer.
This implementation works properly for normal commands, but when used with separate metadata, it crashes at blk_mq_start_request.
Any help or information regarding this would be useful.
linux-kernel
linux-kernel
New contributor
New contributor
New contributor
asked 10 mins ago
anujsingh.kr
1
1
New contributor
New contributor
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
anujsingh.kr is a new contributor. Be nice, and check out our Code of Conduct.
anujsingh.kr is a new contributor. Be nice, and check out our Code of Conduct.
anujsingh.kr is a new contributor. Be nice, and check out our Code of Conduct.
anujsingh.kr is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478340%2fseperate-metadata-support%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password