[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] Refactor AIO to allow multiple AIO implementati
|
From: |
Blue Swirl |
|
Subject: |
Re: [Qemu-devel] [PATCH] Refactor AIO to allow multiple AIO implementations |
|
Date: |
Tue, 16 Sep 2008 20:50:27 +0300 |
On 9/16/08, Anthony Liguori <address@hidden> wrote:
> This patch refactors the AIO layer to allow multiple AIO implementations.
> It's
> only possible because of the recent signalfd() patch.
> +/* This is a simple lock used to protect the aio_handlers list.
> Specifically,
> + * it's used to ensure that no callbacks are removed while we're walking and
> + * dispatching callbacks.
> + */
> +static int walking_handlers;
Shouldn't this be volatile and/or atomic_t?
Just wondering, why don't you use real locking operations, for example
those in qemu-lock.h?