From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulrich Drepper Subject: Re: [take24 0/6] kevent: Generic event handling mechanism. Date: Wed, 22 Nov 2006 13:02:00 -0800 Message-ID: <4564BAC8.6020306@redhat.com> References: <45564EA5.6020607@redhat.com> <20061113105458.GA8182@2ka.mipt.ru> <4560F07B.10608@redhat.com> <20061120082500.GA25467@2ka.mipt.ru> <4562102B.5010503@redhat.com> <20061121095302.GA15210@2ka.mipt.ru> <45633049.2000209@redhat.com> <20061121174334.GA25518@2ka.mipt.ru> <20061121184605.GA7787@2ka.mipt.ru> <4563FE71.4040807@redhat.com> <20061122104416.GD11480@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Miller , Andrew Morton , netdev , Zach Brown , Christoph Hellwig , Chase Venters , Johann Borck , linux-kernel@vger.kernel.org, Jeff Garzik , Alexander Viro Return-path: To: Evgeniy Polyakov In-Reply-To: <20061122104416.GD11480@2ka.mipt.ru> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Evgeniy Polyakov wrote: > But in this case it will be impossible to have SIGEV_THREAD and SIGEV= _KEVENT > at the same time, it will be just the same as SIGEV_SIGNAL but with > different delivery mechanism. Is is what you expect for that? Yes, that's expected. The event if for the queue, not directed to a=20 specific thread. If in future we want to think about preferably waking a specific thread= =20 we can then think about it. But I doubt that'll be beneficial. The=20 thread specific part in the signal handling is only used to implement=20 the SIGEV_THREAD notification. --=20 =E2=9E=A7 Ulrich Drepper =E2=9E=A7 Red Hat, Inc. =E2=9E=A7 444 Castro S= t =E2=9E=A7 Mountain View, CA =E2=9D=96