From: Roland Dreier <rdreier@cisco.com>
To: adi hodos <thefatredguy@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suggested addition to epoll interface - epoll_post_notification()
References: <2517f1930909150559p505b583fpf3501a1c7dad6634@mail.gmail.com>
Date: Tue, 15 Sep 2009 11:16:49 -0700
In-Reply-To: <2517f1930909150559p505b583fpf3501a1c7dad6634@mail.gmail.com>
	(adi hodos's message of "Tue, 15 Sep 2009 15:59:00 +0300")
Message-ID: <adak500f4z2.fsf@cisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 784
Lines: 17


 > I have been playing with epoll lately and I would like to make a suggestion
 > regarding the epoll interface.
 > It would be nice to have a function to wake up a thread/process that is blocked
 > on an epoll_wait() call and sent it some
 > user defined data in the form of a struct epoll_event parameter ( something
 > similar with PostQueuedCompletionStatus() from Windows ).

You might have a look at eventfd() which creates an fd that can be used
to signal from one thread to another (and which can be waited on with epoll).

 - R.
--
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/