This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1869169 - [RFE] [NetKVM] Move Windows virtio-net driver to new MS NIC framework - WDF CX
Summary: [RFE] [NetKVM] Move Windows virtio-net driver to new MS NIC framework - WDF CX
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.2
Hardware: Unspecified
OS: Windows
unspecified
low
Target Milestone: rc
: 9.2
Assignee: ybendito
QA Contact: Wenkang Ji
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 07:13 UTC by Yvugenfi@redhat.com
Modified: 2023-08-15 11:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-15 11:37:28 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1291 0 None None None 2023-08-15 11:37:28 UTC

Description Yvugenfi@redhat.com 2020-08-17 07:13:51 UTC 
Description of problem:
Microsoft created an extension for WDF framework allowing the development of NIC drivers with WDF. We want to move the new framework to enjoy performance advantages 
https://docs.microsoft.com/en-us/windows-hardware/drivers/netcx/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 RHEL Program Management 2022-02-17 07:27:23 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 8 RHEL Program Management 2023-04-30 07:28:11 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.