From owner-freebsd-threads@FreeBSD.ORG Mon Aug 8 11:07:19 2011 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 736E31065670 for ; Mon, 8 Aug 2011 11:07:19 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 480AF8FC0C for ; Mon, 8 Aug 2011 11:07:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p78B7J4U078697 for ; Mon, 8 Aug 2011 11:07:19 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p78B7I6f078695 for freebsd-threads@FreeBSD.org; Mon, 8 Aug 2011 11:07:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Aug 2011 11:07:18 GMT Message-Id: <201108081107.p78B7I6f078695@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-threads@FreeBSD.org 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: Mon, 08 Aug 2011 11:07:19 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o threa/157040 threads [libthr] valgrind detects leaks in libthr.so.3 o threa/154893 threads pthread_sigmask don't work if mask and oldmask are pas o threa/150959 threads [libc] Stub pthread_once in libc should call _libc_onc o threa/149366 threads pthread_cleanup_pop never runs the configured routine o threa/148515 threads Memory / syslog strangeness in FreeBSD 8.x ( possible o threa/141721 threads rtprio(1): (id|rt)prio priority resets when new thread o threa/136345 threads Recursive read rwlocks in thread A cause deadlock with o threa/135673 threads databases/mysql50-server - MySQL query lock-ups on 7.2 o threa/128922 threads threads hang with xorg running o threa/127225 threads bug in lib/libthr/thread/thr_init.c o threa/122923 threads 'nice' does not prevent background process from steali o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7 o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP o threa/115211 threads pthread_atfork misbehaves in initial thread o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/101323 threads [patch] fork(2) in threaded programs broken. s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/79683 threads svctcp_create() fails if multiple threads call at the s threa/76694 threads fork cause hang in dup()/close() function in child (-l s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/34536 threads accept() blocks other threads s threa/30464 threads [patch] pthread mutex attributes -- pshared 25 problems total. From owner-freebsd-threads@FreeBSD.ORG Thu Aug 11 10:36:29 2011 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDEE01065670 for ; Thu, 11 Aug 2011 10:36:29 +0000 (UTC) (envelope-from adi.ninad@gmail.com) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id AE44E8FC14 for ; Thu, 11 Aug 2011 10:36:29 +0000 (UTC) Received: by iye7 with SMTP id 7so3163173iye.17 for ; Thu, 11 Aug 2011 03:36:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=P3vnzCn5lbvgpq2o6REqn5DLwWeqN/hBtEJIaRTcyDg=; b=HXSAR7HIuQIcVQNz/7XC2/tVee//Lvh+vW3lVGl8dPsh0DAEmydFJ51RdxG8sJkjXM vdV8pN/21LNRkkghNr21YfmezvquMYh9L5UExnsQzzXgGqbVe6aVhlwshRrjy5iiAVpO 3xwkfrSmYu3RpYUnFfVqj0WK329s3Nw27ELrw= MIME-Version: 1.0 Received: by 10.231.114.198 with SMTP id f6mr12044257ibq.77.1313057625421; Thu, 11 Aug 2011 03:13:45 -0700 (PDT) Received: by 10.231.63.198 with HTTP; Thu, 11 Aug 2011 03:13:45 -0700 (PDT) Date: Thu, 11 Aug 2011 15:43:45 +0530 Message-ID: From: Ninad Adi To: "freebsd-threads@freebsd.org" X-Mailman-Approved-At: Thu, 11 Aug 2011 11:07:34 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Urgent interrupt thread 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: Thu, 11 Aug 2011 10:36:29 -0000 To, Freebsd greats, Dear sirs, In freebsd 8.2 kernel architecture Do interrupt handlers run as threads by default or do they run in interrupt context ?? Ninad. Freebsd developer. From owner-freebsd-threads@FreeBSD.ORG Fri Aug 12 08:59:19 2011 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBD34106564A; Fri, 12 Aug 2011 08:59:19 +0000 (UTC) (envelope-from adi.ninad@gmail.com) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id 884E58FC08; Fri, 12 Aug 2011 08:59:19 +0000 (UTC) Received: by iye7 with SMTP id 7so5239757iye.17 for ; Fri, 12 Aug 2011 01:59:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3F6WW8gvQ8PS8TnrGxUMnsMWf8V1/QAeCx/x0BMkAFo=; b=bETSrA2eKx/eKrNOcCbHE6b0oxBwM8DCT09KfomPv7+yq2vgAO4Ak7DqDWQmgkSY4l 8u40FI6XA8n+MbGowYre/ASVwQEVboVwZgHlqqumGx0mGSoeVDxN34E7lnQpSwhfDEiT I34RKbzIxnTAGNWWs3fv8gVeYnFlpq5AQK2U8= MIME-Version: 1.0 Received: by 10.231.83.135 with SMTP id f7mr1389065ibl.90.1313139558816; Fri, 12 Aug 2011 01:59:18 -0700 (PDT) Received: by 10.231.63.198 with HTTP; Fri, 12 Aug 2011 01:59:18 -0700 (PDT) In-Reply-To: <4E44E326.9070405@freebsd.org> References: <4E44CBA6.9050809@freebsd.org> <4E44E326.9070405@freebsd.org> Date: Fri, 12 Aug 2011 14:29:18 +0530 Message-ID: From: Ninad Adi To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-threads@freebsd.org" Subject: Re: Urgent interrupt thread 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: Fri, 12 Aug 2011 08:59:19 -0000 Thanks for your prompt replies sir, just one more clarification the routine bus_setup_intr has 5th arg of type driver_intr_t ithread then if I am not wrong my isr is running as a thread, probably thats the reason why latest drivers dont use Deferring mechanism like iwi, iwn, ral. However Atheros is still using taskqueues which is considerably old I suppose. So using filter+ithread model without deferring Should be fine. Plz let me know your opinions on the same, It would help me understand freebsd better. Will not disturb you more. Awaiting,reply Thanks a lot, Ninad Adi. On Friday, August 12, 2011, Julian Elischer wrote: > On 8/12/11 12:45 AM, Ninad Adi wrote: > > So in the routine bus_setup_intr the isr runs as > ithread but then if its a thread why its not allowed to sleep it aquires mutex lock , disables > all interrupts and continues. > > > if it is running as an ithread it can do those things. > if it is running as a fast interrupt handler it can't. > the driver sets how the code is to be run > > > > My last question is in that case do we need to > Use taskqueues or we can completely write the > Isr in one thread itself without using deferring > Primitives. I.e can we refrain from using deferring mechanism. > > if you use an ithread you can do what you want.. > > http://www.unix.com/man-page/FreeBSD/9/ithread/ > > > > > awaiting the reply. > > Ninad Adi. > > > On Friday, August 12, 2011, Julian Elischer wrote: >> On 8/11/11 3:13 AM, Ninad Adi wrote: >>> >>> To, >>> Freebsd greats, >>> >>> Dear sirs, >>> In freebsd 8.2 kernel architecture >>> Do interrupt handlers run as threads by >>> default or do they run in interrupt context ?? >>> >>> Ninad. >>> Freebsd developer. >>> _______________________________________________ >>> freebsd-threads@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-threads < http://lists.freebsd.org/mailman/listinfo/freebsd-threads> >>> To unsubscribe, send any mail to " freebsd-threads-unsubscribe@freebsd.org" >>> >> you have the choice to do either. >> >> >> key words to look up are 'fast' interrupts and "interrrupt threads" >> >> I've not used either for many years. so I hope that helps enough that you can find hte right answer. >> >> >> >> > From owner-freebsd-threads@FreeBSD.ORG Fri Aug 12 07:45:23 2011 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B660106566C for ; Fri, 12 Aug 2011 07:45:23 +0000 (UTC) (envelope-from adi.ninad@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id DC90E8FC1B for ; Fri, 12 Aug 2011 07:45:22 +0000 (UTC) Received: by ywo32 with SMTP id 32so972852ywo.13 for ; Fri, 12 Aug 2011 00:45:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HUFd8Up5HUdUL/B+PLZy1VE6nBGb2I/+jQegf9ZIddw=; b=BlUt92cWUO98gfW1pTzt1Rkn10eP2WeY0yp2B+ep4NDowF0rEUFmLTzDHpb+Hcah8P +ieoGavD1b3pF/V5/MdCWoLKajMtcrWS84msh7nz8EEEZXnpaHU/RMzj2LzP1RgsvImj C0+FwQgWplj9dqxt1CHxWtyvQifK6lpLNm+xI= MIME-Version: 1.0 Received: by 10.43.132.131 with SMTP id hu3mr68749icc.185.1313135122006; Fri, 12 Aug 2011 00:45:22 -0700 (PDT) Received: by 10.231.63.198 with HTTP; Fri, 12 Aug 2011 00:45:21 -0700 (PDT) In-Reply-To: <4E44CBA6.9050809@freebsd.org> References: <4E44CBA6.9050809@freebsd.org> Date: Fri, 12 Aug 2011 13:15:21 +0530 Message-ID: From: Ninad Adi To: Julian Elischer X-Mailman-Approved-At: Fri, 12 Aug 2011 11:18:13 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-threads@freebsd.org" Subject: Re: Urgent interrupt thread 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: Fri, 12 Aug 2011 07:45:23 -0000 So in the routine bus_setup_intr the isr runs as ithread but then if its a thread why its not allowed to sleep it aquires mutex lock , disables all interrupts and continues. My last question is in that case do we need to Use taskqueues or we can completely write the Isr in one thread itself without using deferring Primitives. I.e can we refrain from using deferring mechanism. awaiting the reply. Ninad Adi. On Friday, August 12, 2011, Julian Elischer wrote: > On 8/11/11 3:13 AM, Ninad Adi wrote: >> >> To, >> Freebsd greats, >> >> Dear sirs, >> In freebsd 8.2 kernel architecture >> Do interrupt handlers run as threads by >> default or do they run in interrupt context ?? >> >> Ninad. >> Freebsd developer. >> _______________________________________________ >> freebsd-threads@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-threads < http://lists.freebsd.org/mailman/listinfo/freebsd-threads> >> To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org " >> > you have the choice to do either. > > > key words to look up are 'fast' interrupts and "interrrupt threads" > > I've not used either for many years. so I hope that helps enough that you can find hte right answer. > > > >