Date: Tue, 28 Feb 2006 21:27:51 -0500
From: Benjamin LaHaise <bcrl@kvack.org>
To: "Li, Peng" <ringer9cs@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Thread safety for epoll/libaio
Message-ID: <20060301022751.GA28899@kvack.org>
References: <598a055d0602281236m7eac9c09oc60af9ce28e7e4bf@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <598a055d0602281236m7eac9c09oc60af9ce28e7e4bf@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 22

On Tue, Feb 28, 2006 at 03:36:11PM -0500, Li, Peng wrote:
> I apologize if I should not post this on LKML, but there seems to be
> some lack of documentation for using epoll/AIO with threads.  Are
> these interfaces thread-safe?  Can I use them safely in the following
> way:

I can only speak for libaio, which is completely thread safe.  Having a 
single thread read events and dispatch is likely to work quite well given 
the way the kernel interface is structured internally.  There is still 
room for improving the event mechanism to use a futex for waking so that 
the library can parse multiple events from userspace, but that is pending 
a heavier user like networking.

		-ben
-- 
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here 
and they've asked us to stop the party."  Don't Email: <dont@kvack.org>.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/