All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH][RFC] Linux AIO support when using O_DIRECT
Date: Mon, 23 Mar 2009 15:32:02 -0500	[thread overview]
Message-ID: <49C7F1C2.2010001@codemonkey.ws> (raw)
In-Reply-To: <49C7E9CE.50506@redhat.com>

Avi Kivity wrote:
>
>>
>> We would drop the signaling stuff and have the thread pool use an fd 
>> to signal.  The big problem with that right now is that it'll cause a 
>> performance regression for certain platforms until we have the IO 
>> thread in place. 
>
> Well, let's merge this after the iothread?

Yup.  Just posted that patch in case anyone was interested.  I needed it 
so that we could do some performance testing...

Regards,

Anthony Liguori


  reply	other threads:[~2009-03-23 20:32 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
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 [this message]
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=49C7F1C2.2010001@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=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.