All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH][RFC] Linux AIO support when using O_DIRECT
Date: Mon, 23 Mar 2009 18:17:36 +0200	[thread overview]
Message-ID: <49C7B620.8030203@redhat.com> (raw)
In-Reply-To: <1237823124-6417-1-git-send-email-aliguori@us.ibm.com>

Anthony Liguori wrote:
> This is just a first cut.  It needs a fair bit of cleanup before it can be
> committed.  I also think we need to fixup the AIO abstractions a bit.
>
> I wanted to share though in case anyone is interested in doing some performance
> comparisons.  It seems to work although I haven't exercised it very much.
>
>  
> +typedef struct AIOOperations
> +{
> +    struct qemu_aiocb *(*get_aiocb)(void);
> +    void (*put_aiocb)(struct qemu_aiocb *);
> +    int (*read)(struct qemu_aiocb *);
> +    int (*write)(struct qemu_aiocb *);
> +    int (*error)(struct qemu_aiocb *);
> +    ssize_t (*get_result)(struct qemu_aiocb *aiocb);
> +    int (*cancel)(int fd, struct qemu_aiocb *aiocb);
> +} AIOOperations;
> +
>   


Instead of introducing yet another layer of indirection, you could add 
block-raw-linux-aio, which would be registered before block-raw-posix 
(which is realy block-raw-threadpool...), and resist a ->probe() if 
caching is enabled.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-03-23 16:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 15:45 [PATCH][RFC] Linux AIO support when using O_DIRECT Anthony Liguori
2009-03-23 15:45 ` [Qemu-devel] " Anthony Liguori
2009-03-23 16:17 ` Avi Kivity [this message]
2009-03-23 17:14   ` Anthony Liguori
2009-03-23 17:29     ` Christoph Hellwig
2009-03-23 17:29       ` Christoph Hellwig
2009-03-23 18:10       ` Anthony Liguori
2009-03-23 18:10         ` Anthony Liguori
2009-03-23 18:48         ` Christoph Hellwig
2009-03-23 19:35           ` Avi Kivity
2009-03-23 19:35             ` Avi Kivity
2009-03-23 17:32     ` Christoph Hellwig
2009-03-23 17:32       ` Christoph Hellwig
2009-03-23 19:58     ` Avi Kivity
2009-03-23 20:32       ` Anthony Liguori
2009-03-23 17:26   ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49C7B620.8030203@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.