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.

Bug 803985

Summary:	[virtio-win][balloon]the speed of enlarging memory is much faster than the speed of evicting memory
Product:	Red Hat Enterprise Linux 6	Reporter:	Mike Cao <bcao>
Component:	virtio-win	Assignee:	Vadim Rozenfeld <vrozenfe>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	acathrow, amit.shah, bsarathy, dawu, mdeng, michen, rhod
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-18 11:01:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Cao 2012-03-16 08:25:36 UTC

Description of problem:


Version-Release number of selected component (if applicable):
2.6.32-252.el6.x86_64
qemu-kvm-0.12.1.2-2.248.el6rhev.x86_64
virtio-win-prewhql-23


How reproducible:
100%

Steps to Reproduce:
1.start guest with -m 8G
2.(qemu)balloon 1024
3.after step ,(qemu)balloon 8192
  
Actual results:
the speed of evicting memory is 53MB/Sec
the speed of enlarging memroy is 700MB/Sec

Expected results:
the speed of evicting memory and enlaring memory should be same .


Additional info:

Comment 2 Vadim Rozenfeld 2012-03-18 11:01:37 UTC

(In reply to comment #0)
> Description of problem:
> 
> 
> Version-Release number of selected component (if applicable):
> 2.6.32-252.el6.x86_64
> qemu-kvm-0.12.1.2-2.248.el6rhev.x86_64
> virtio-win-prewhql-23
> 
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1.start guest with -m 8G
> 2.(qemu)balloon 1024
> 3.after step ,(qemu)balloon 8192
> 
> Actual results:
> the speed of evicting memory is 53MB/Sec
> the speed of enlarging memroy is 700MB/Sec
> 
> Expected results:
> the speed of evicting memory and enlaring memory should be same .

Let me disagree, allocating memory from and releasing memory to non-paged
pool are not equal process in any terms. So you cannot expect both of
them to be performed at the same speed. BTW, while allocating (ballon inflating)
speed will vary, depending on the balloon size, size of free memory, and system load.    

Best regards,
Vadim.
 
> 
> 
> Additional info: