Thread (50 messages) 50 messages, 6 authors, 2011-02-24

Re: [RFC PATCH 0/2] Expose available KVM free memory slot count to help avoid aborts

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2011-01-26 09:20:57

On Wed, Jan 26, 2011 at 11:17:11AM +0200, Avi Kivity wrote:
On 01/25/2011 07:58 PM, Michael S. Tsirkin wrote:
quoted
On Tue, Jan 25, 2011 at 07:33:40PM +0200, Avi Kivity wrote:
quoted
 On 01/25/2011 04:59 PM, Michael S. Tsirkin wrote:
 >On Tue, Jan 25, 2011 at 04:53:44PM +0200, Avi Kivity wrote:
 >>   For the other lookups, which we
 >>   believe will succeed, we can assume the probablity of a match is
 >>   related to the slot size, and sort the slots by page count.
 >
 >Unlikely to be true for assigned device BARs.

 We'll have a large slot at 4G+ - EOM, a medium slot at 1M-3G, and
 lots of small slots for BARs and such.

 The vast majority of faults will either touch one of the two largest
 slots, or will miss all slots.  Relatively few will hit the small
 slots.
Not if you are using one of the assigned devices and don't
do any faults on memory :)
It's impossible not to fault on memory.
No I mean the RAM.
-- 
error compiling committee.c: too many arguments to function
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help