On 08/12/2011 06:24 AM, Anthony Liguori wrote:
On 08/08/2011 06:37 AM, Avi Kivity wrote:
+static void spawn_thread_bh_fn(void *opaque)
+{
+mutex_lock(&lock);
+do_spawn_thread();
+mutex_unlock(&lock);
+}
The locking here is odd. Why not call do_spawn_thread() without the
lock, an
On 08/08/2011 06:37 AM, Avi Kivity wrote:
In certain circumstances, posix-aio-compat can incur a lot of latency:
- threads are created by vcpu threads, so if vcpu affinity is set,
aio threads inherit vcpu affinity. This can cause many aio threads
to compete for one cpu.
- we can crea
On 08/08/2011 04:21 PM, Frediano Ziglio wrote:
>
> The entire qemu process may be affined to a subset of the host cpus; we
> don't want to break that.
>
> For example:
>
> taskset 0xf0 qemu
> (qemu) info cpus
>
>
>
Just call sched_getaffinity at program start, save to a global
2011/8/8 Avi Kivity :
> On 08/08/2011 03:49 PM, Frediano Ziglio wrote:
>>
>> 2011/8/8 Avi Kivity:
>> > In certain circumstances, posix-aio-compat can incur a lot of latency:
>> > - threads are created by vcpu threads, so if vcpu affinity is set,
>> > aio threads inherit vcpu affinity. This
On 08/08/2011 03:49 PM, Frediano Ziglio wrote:
2011/8/8 Avi Kivity:
> In certain circumstances, posix-aio-compat can incur a lot of latency:
>- threads are created by vcpu threads, so if vcpu affinity is set,
> aio threads inherit vcpu affinity. This can cause many aio threads
> to
2011/8/8 Avi Kivity :
> In certain circumstances, posix-aio-compat can incur a lot of latency:
> - threads are created by vcpu threads, so if vcpu affinity is set,
> aio threads inherit vcpu affinity. This can cause many aio threads
> to compete for one cpu.
> - we can create up to max_threa
On 08/08/2011 03:34 PM, Anthony Liguori wrote:
On 08/08/2011 06:37 AM, Avi Kivity wrote:
In certain circumstances, posix-aio-compat can incur a lot of latency:
- threads are created by vcpu threads, so if vcpu affinity is set,
aio threads inherit vcpu affinity. This can cause many aio thr
On 08/08/2011 06:37 AM, Avi Kivity wrote:
In certain circumstances, posix-aio-compat can incur a lot of latency:
- threads are created by vcpu threads, so if vcpu affinity is set,
aio threads inherit vcpu affinity. This can cause many aio threads
to compete for one cpu.
- we can crea
In certain circumstances, posix-aio-compat can incur a lot of latency:
- threads are created by vcpu threads, so if vcpu affinity is set,
aio threads inherit vcpu affinity. This can cause many aio threads
to compete for one cpu.
- we can create up to max_threads (64) aio threads in one go;
