qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Antonio Vargas" <windenntw@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH 1/3] Refactor AIO interface to allow other AIO implementations
Date: Fri, 2 May 2008 17:37:05 +0100	[thread overview]
Message-ID: <69304d110805020937l2f867cadrd7c906b8eb77b3f6@mail.gmail.com> (raw)
In-Reply-To: <20080422153616.GC10229@shareable.org>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

On Tue, Apr 22, 2008 at 4:36 PM, Jamie Lokier <jamie@shareable.org> wrote:

*snip*


>
> Btw, regarding QEMU: QEMU gets requests _after_ sorting by the guest's
> elevator, then submits them to the host's elevator.  If the guest and
> host elevators are both configured 'anticipatory', do the anticipatory
> delays add up?
>


Anticipatory is non-work-conserving. If the data is going to end passing
thru
host's deadline scheduler, probably it is better to the guest with deadline
or maybe even no-op since it doesn't really know anything about the real
disk locations of the data.

-- 
Greetz, Antonio Vargas aka winden of rgba^ntw^bg

http://winden.wordpress.com/
windenntw@gmail.com

Every day, every year
you have to work
you have to study
you have to scene.

[-- Attachment #2: Type: text/html, Size: 1187 bytes --]

  reply	other threads:[~2008-05-02 16:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 19:26 [Qemu-devel] [PATCH 1/3] Refactor AIO interface to allow other AIO implementations Anthony Liguori
2008-04-17 19:26 ` [Qemu-devel] [PATCH 2/3] Split out posix-aio code Anthony Liguori
2008-04-17 19:26 ` [Qemu-devel] [PATCH 3/3] Implement linux-aio backend Anthony Liguori
2008-04-18 15:09   ` [Qemu-devel] " Marcelo Tosatti
2008-04-18 15:18     ` Anthony Liguori
2008-04-18 17:46       ` Marcelo Tosatti
2008-04-17 19:38 ` [Qemu-devel] Re: [kvm-devel] [PATCH 1/3] Refactor AIO interface to allow other AIO implementations Daniel P. Berrange
2008-04-17 19:41   ` Anthony Liguori
2008-04-17 20:00     ` Daniel P. Berrange
2008-04-17 20:05       ` Anthony Liguori
2008-04-18 12:43       ` Jamie Lokier
2008-04-18 15:23         ` Anthony Liguori
2008-04-18 16:22           ` Jamie Lokier
2008-04-18 16:32           ` [kvm-devel] [Qemu-devel] " Avi Kivity
2008-04-20 15:49             ` Jamie Lokier
2008-04-20 18:43               ` Avi Kivity
2008-04-20 23:39                 ` Jamie Lokier
2008-04-21  6:39                   ` Avi Kivity
2008-04-21 12:10                     ` Jamie Lokier
2008-04-22  8:10                       ` Avi Kivity
2008-04-22 14:28                         ` Jamie Lokier
2008-04-22 14:53                           ` Anthony Liguori
2008-04-22 15:05                             ` Avi Kivity
2008-04-22 15:23                               ` Jamie Lokier
2008-04-22 15:12                             ` Jamie Lokier
2008-04-22 15:03                           ` Avi Kivity
2008-04-22 15:36                             ` Jamie Lokier
2008-05-02 16:37                               ` Antonio Vargas [this message]
2008-05-02 17:18                                 ` Jamie Lokier
2008-05-02 17:52                                   ` Anthony Liguori
2008-05-02 18:24                                     ` Jamie Lokier

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=69304d110805020937l2f867cadrd7c906b8eb77b3f6@mail.gmail.com \
    --to=windenntw@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).