Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261394AbVEDTQR (ORCPT ); Wed, 4 May 2005 15:16:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261389AbVEDTQR (ORCPT ); Wed, 4 May 2005 15:16:17 -0400 Received: from nevyn.them.org ([66.93.172.17]:35205 "EHLO nevyn.them.org") by vger.kernel.org with ESMTP id S261394AbVEDTQG (ORCPT ); Wed, 4 May 2005 15:16:06 -0400 Date: Wed, 4 May 2005 15:16:04 -0400 From: Daniel Jacobowitz To: "Richard B. Johnson" Cc: Olivier Croquette , LKML Subject: Re: Scheduler: SIGSTOP on multi threaded processes Message-ID: <20050504191604.GA29730@nevyn.them.org> Mail-Followup-To: "Richard B. Johnson" , Olivier Croquette , LKML References: <4279084C.9030908@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 26 On Wed, May 04, 2005 at 02:16:24PM -0400, Richard B. Johnson wrote: > The kernel doesn't do SIGSTOP or SIGCONT. Within init, there is > a SIGSTOP and SIGCONT handler. These can be inherited by others > unless changed, perhaps by a 'C' runtime library. Basically, > the SIGSTOP handler executes pause() until the SIGCONT signal > is received. > > Any delay in stopping is the time necessary for the signal to > be delivered. It is possible that the section of code that > contains the STOP/CONT handler was paged out and needs to be > paged in before the signal can be delivered. > > You might quicken this up by installing your own handler for > SIGSTOP and SIGCONT.... I don't know what RTOSes you've been working with recently, but none of the above is true for Linux. I don't think it ever has been. -- Daniel Jacobowitz CodeSourcery, LLC - 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/