Bug 1339175
Summary: | [NetKVM] Turn on RSC feature in NetKVM driver | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yvugenfi <yvugenfi> |
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> |
virtio-win sub component: | virtio-win-prewhql | QA Contact: | Virtualization Bugs <virt-bugs> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | jen, juzhang, lijin, lmiksik, lprosek, wyu, yvugenfi |
Version: | 7.3 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
This update adds support for the RSC feature to the virtio-net (NetKVM) Windows guest driver. The support is included in all driver versions targeted at Windows Server 2012 and up. RSC (Receive Segment Coalescing) enables the driver to report coalesced TCP segments to the OS.
https://msdn.microsoft.com/en-us/windows/hardware/drivers/network/receive-segment-coalescing--rsc-
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 08:54:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yvugenfi@redhat.com
2016-05-24 10:27:45 UTC
What does make this bug security sensitive? (In reply to Adam Mariš from comment #1) > What does make this bug security sensitive? It is not security sensitive. I don't know why there is "security" in keywords field. I am removing it to prevent confusion. with virtio-win-prewhql-126,rsc feature is turned on,rsc related job can be loaded when run netkvm whql test.And job can pass(with filter/errata) So change status to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2609.html |