From owner-freebsd-threads@FreeBSD.ORG Wed Feb 10 17:25:58 2010 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D9B11065692; Wed, 10 Feb 2010 17:25:58 +0000 (UTC) (envelope-from rrs@lakerest.net) Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by mx1.freebsd.org (Postfix) with ESMTP id 9F25A8FC1B; Wed, 10 Feb 2010 17:25:57 +0000 (UTC) Received: from mobile-166-129-159-005.mycingular.net (mobile-166-129-159-005.mycingular.net [166.129.159.5] (may be forged)) (authenticated bits=0) by lakerest.net (8.14.3/8.14.3) with ESMTP id o1AHP0EU009136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 10 Feb 2010 12:25:54 -0500 (EST) (envelope-from rrs@lakerest.net) Message-Id: <3CF3033E-FD13-405B-9DC6-DDE9DF4FBF37@lakerest.net> From: Randall Stewart To: Daniel Eischen In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 10 Feb 2010 09:25:52 -0800 References: <3581A86D-9C9C-4E08-9AD3-CD550B180CED@lakerest.net> X-Mailer: Apple Mail (2.936) Cc: threads@freebsd.org Subject: Re: Thinking about kqueue's and pthread_cond_wait X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2010 17:25:58 -0000 On Feb 10, 2010, at 9:04 AM, Daniel Eischen wrote: > On Wed, 10 Feb 2010, Randall Stewart wrote: > >> All: >> >> I have once again come around to thinking about joining pthread >> cond waits and >> kqueue's. >> >> After thinking about it, I think its doable.. with something like a: >> >> pthread_cond_wait_kqueue_np(kev, cond, mtx, ucontext) >> >> Then you can use kev inside a kqueue i.e. >> ret = kevent(kq, kev, 1, outkev, 1, NULL); >> >> Now when you saw the event: >> if (kev.filter == EVFILT_UMTX){ /* not sure about the name here */ >> pthread_kqueue_cond_wait_ret_np(kev, cond, mtx, ucontext) >> do_user_action(cond,mtx, ucontext); >> } >> >> Which would fill in the cond/mtx and ucontext for the user. >> >> Now does this sound useful to anyone.. i.e. should I spend the time >> making it work? >> >> The only down side to this is that it would have to allocate memory >> so >> one would need to do a: >> >> pthread_kqueue_cond_wait_free_np(kev) >> >> After you were done.. and I think it would be best for this to >> be a ONE_SHOT.. i.e. you have to re-arm it if the event happens... >> Of course until you free it that can be as simple as passing the kev >> back down again (i.e. no pthread_cond_wait_kqueue_np() needed). >> >> Comments? Thoughts? i.e. especially is it worthwhile doing? > > Please don't mess with the pthread_ API like that :-) If you > really want to munge them together, see my email to you a few > weeks ago last time you brought it up.' If I remember right your email was basically don't do it... I will go dig through the archives and re-read it all. R > > -- > DE > ------------------------------ Randall Stewart 803-317-4952 (cell) 803-345-0391(direct)