All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Bernhard Schmidt <berni@birkenwald.de>,
	kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: linux-aio usable?
Date: Tue, 09 Mar 2010 11:09:47 +0200	[thread overview]
Message-ID: <4B96105B.50402@redhat.com> (raw)
In-Reply-To: <20100308212736.GB4731@nik-comp.linuxbox.cz>

On 03/08/2010 11:27 PM, Nikola Ciprich wrote:
>> It's faster.
>>      
> Hi Avi,
> Could You give some rough estimate on how much faster?
>    

The standard "it depends on the workload".

> I'm stuck with glibc-2.5 now, but I'm always eager to improve performance,
> so I wonder if it would make sense to either port eventfd + aio stuff, or
> switch to glibc-2.8 for me...
>    

Switching to a modern setup should be much easier and safer.  Esp. a 
modern kernel.

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


      parent reply	other threads:[~2010-03-09  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08  1:46 linux-aio usable? Bernhard Schmidt
2010-03-08  9:10 ` Avi Kivity
2010-03-08  9:48   ` Bernhard Schmidt
2010-03-08  9:48     ` Avi Kivity
2010-03-08 14:25       ` Dustin Kirkland
2010-03-08 14:26         ` Avi Kivity
2010-03-08 16:28           ` Anthony Liguori
2010-03-08 16:36             ` Avi Kivity
2010-03-08 13:00   ` Christoph Hellwig
2010-03-08 20:11   ` Michael Tokarev
2010-03-08 20:19     ` Michael Tokarev
2010-03-09  9:08       ` Avi Kivity
2010-03-09  9:19         ` Michael Tokarev
2010-03-09 10:05           ` Avi Kivity
2010-03-09 14:12             ` Christoph Hellwig
2010-03-08 21:27   ` Nikola Ciprich
2010-03-08 21:46     ` Brian Jackson
2010-03-09  9:09     ` Avi Kivity [this message]

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=4B96105B.50402@redhat.com \
    --to=avi@redhat.com \
    --cc=berni@birkenwald.de \
    --cc=extmaillist@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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.