From: Evgeniy Polyakov Subject: Re: [take19 0/4] kevent: Generic event handling mechanism. Date: Wed, 4 Oct 2006 08:55:27 +0400 Message-ID: <20061004045527.GB32267@2ka.mipt.ru> References: <115a6230591036@2ka.mipt.ru> <11587449471424@2ka.mipt.ru> <20060927150957.GA18116@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Cc: lkml , David Miller , Ulrich Drepper , Andrew Morton , netdev , Zach Brown , Christoph Hellwig , Chase Venters Return-path: Received: from relay.2ka.mipt.ru ([194.85.82.65]:41947 "EHLO 2ka.mipt.ru") by vger.kernel.org with ESMTP id S1160996AbWJDEz5 (ORCPT ); Wed, 4 Oct 2006 00:55:57 -0400 To: Ulrich Drepper Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, Oct 03, 2006 at 09:50:09PM -0700, Ulrich Drepper (drepper@gmail.com) wrote: > On 9/27/06, Evgeniy Polyakov wrote: > \> I have been told in private what is signal masks about - just to wait > >until either signal or given condition is ready, but in that case just > >add additional kevent user like AIO complete or netwrok notification > >and wait until either requested events are ready or signal is triggered. > > No, this won't work. Yes, I want signal notification as part of the > event handling. But there are situations when this is not suitable. > Only if the signal is expected in the same code using the event > handling can you do this. But this is not always possible. > Especially when the signal handling code is used in other parts of the > code than the event handling. E.g., signal handling in a library, > event handling in the main code. You cannot assume that all the code > is completely integrated. Signals still can be delivered in usual way too. When we enter sys_ppoll() we specify needed signals as syscall parameter, with kevents we will add them into the queue. -- Evgeniy Polyakov