At 2004-09-27T11:50:28+0200, Hallingstad Håkon wrote:
FYI: aiotest is working fine on my SuSE 9.1 Personal box.
Interesting, thanks for testing that. I've just done a minimal SuSE 9.1 install and do see the problem, even after updating to the latest available SuSE kernel. What versions of glibc and the kernel does you 9.1 box have, is your 9.1 box a i686 or better (or some other system where the TLS glibc libraries will be used), and are you running a SuSE kernel? $ rpm -q kernel-default; rpm -q glibc kernel-default-2.6.5-7.108 glibc-2.3.3-97 Thanks, -mjg
-----Original Message----- From: Matthew Gregan [mailto:kinetik@orcon.net.nz] Sent: 27. september 2004 11:33 To: suse-programming-e@suse.com Subject: [suse-programming-e] Problems with POSIX Asynchronous IO
Hi all,
I'm having some problems with the POSIX Asynchronous IO support on a SLES 9 box I've been working with. The machine has all of the available SLES 9 updates applied.
After submitting a single IO using the POSIX AIO interface provided by glibc, I notice that the worker thread created by glibc enters a tight loop and consumes 100% of one CPU. Once this occurs, AIO continues to work fine (other than this problem), but the worker thread will remain in this state until the program exits.
-- Matthew Gregan |/ /| kinetik@orcon.net.nz