From: NyOS <lista@nyos.homelinux.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Win32 MinGW build with current CVS
Date: Wed, 02 Aug 2006 21:07:15 +0200 [thread overview]
Message-ID: <op.tdn7edpmt9pcbo@mail.chello.hu> (raw)
In-Reply-To: <44D0E9F2.1090202@geodb.org>
On Wed, 02 Aug 2006 20:07:46 +0200, Andreas Bollhalder <bolle@geodb.org>
wrote:
> Hello
>
> It seems that the aio support broke my MinGW build batch under Win32. Is
> it suposed to work on WIN32 ?
>
> Any ideas ?
>
> Andreas
...
Hi!
"Kernel Asynchronous I/O (AIO) Support for Linux
Overview
AIO enables even a single application thread to overlap I/O operations
with other processing, by providing an interface for submitting one or
more I/O requests in one system call (io_submit()) without waiting for
completion, and a separate interface (io_getevents()) to reap completed
I/O operations associated with a given completion group.
Support for kernel AIO has been included in the 2.6 Linux kernel."
source:
http://lse.sourceforge.net/io/aio.html
So, I don't think so. But please correct me, if I'm wrong.
Nyos
-------------------------------------------------------
Delay not, Caesar. Read it instantly.
-- Shakespeare, "Julius Caesar" 3,1
Here is a letter, read it at your leisure.
-- Shakespeare, "Merchant of Venice" 5,1
[Quoted in "VMS Internals and Data Structures", V4.4, when
referring to I/O system services.]
next prev parent reply other threads:[~2006-08-02 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 18:07 [Qemu-devel] Win32 MinGW build with current CVS Andreas Bollhalder
2006-08-02 19:07 ` NyOS [this message]
2006-08-03 3:14 ` Kazu
2006-08-03 8:24 ` Kazu
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 8:41 ZIGLIO, Frediano, VF-IT
2006-08-03 8:58 ZIGLIO, Frediano, VF-IT
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=op.tdn7edpmt9pcbo@mail.chello.hu \
--to=lista@nyos.homelinux.net \
--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.