Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

hi, Yan
    
    Can you help check if the issue is reproductive bug with Bug #826596, if not, will it be modified before submitting the microsoft review?

Thanks

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

(In reply to comment #2)
> hi, Yan
>     
>     Can you help check if the issue is reproductive bug with Bug #826596, if
> not, will it be modified before submitting the microsoft review?
> 
> Thanks

Hi,

There will be no changes before WHQL.

Best regards.
Yan.

Fixed by BZ#713130 and BZ#878442

Hi, yan 

We still could see consistent RX performance degression in build-62 on winXP 32 bit guest with default property setting.

plese check "Category:TCP_STREAM (RX)" parts in following reuslts:

1. virtio-win-1.4.0 vs build-62 on under default setting 
http://kvm-perf.englab.nay.redhat.com/results/request/build-62/WinXP.i386.netperf_win.netperf_exe.default_setting.html

2. virtio-win-1.4.0 vs build-62 on under registry setting
http://kvm-perf.englab.nay.redhat.com/results/request/build-62/WinXP.i386.netperf_win.netperf_exe.best_registry_setting.html

Btw, notice that "OffloadRX.checksum /OffloadTx.checksum" are all disalbed by default in build-62 during our tests. Does it as expected?

Based on comment #8 ,re-assign this issue