On Mon, Jul 25, 2011 at 9:56 AM, Paolo Bonzini wrote:
> On 07/19/2011 12:57 PM, Stefan Hajnoczi wrote:
>>
>> From what I understand "committed" on Windows means that physical
>> pages have been allocated and pagefile space has been set aside:
>> http://msdn.microsoft.com/en-us/library/ms810627.as
On 07/19/2011 12:57 PM, Stefan Hajnoczi wrote:
From what I understand "committed" on Windows means that physical
pages have been allocated and pagefile space has been set aside:
http://msdn.microsoft.com/en-us/library/ms810627.aspx
Yes, memory that is "reserved" on Windows is just a contiguous
On 07/19/2011 05:10 AM, Kevin Wolf wrote:
Am 19.07.2011 10:06, schrieb Frediano Ziglio:
They are still all running in the same thread.
2- memory considerations on coroutines. Beside coroutines allow more
readable code I wonder if somebody considered memory. For every
coroutines a different stac
On Tue, Jul 19, 2011 at 11:10 AM, Kevin Wolf wrote:
> Am 19.07.2011 10:06, schrieb Frediano Ziglio:
>> 2- memory considerations on coroutines. Beside coroutines allow more
>> readable code I wonder if somebody considered memory. For every
>> coroutines a different stack has to be allocated. For in
Am 19.07.2011 10:06, schrieb Frediano Ziglio:
> I'm exercise myself in block I/O layer and I decided to test
> coroutine branch cause I find it easier to use instead of normal
> callback. Looking at normal code there are a lot of rows in source to
> save/restore state and declare callbacks and is
Hi,
I'm exercise myself in block I/O layer and I decided to test
coroutine branch cause I find it easier to use instead of normal
callback. Looking at normal code there are a lot of rows in source to
save/restore state and declare callbacks and is not that easier to
understand the normal flow. At
