Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263580AbTIHVMx (ORCPT ); Mon, 8 Sep 2003 17:12:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263584AbTIHVMx (ORCPT ); Mon, 8 Sep 2003 17:12:53 -0400 Received: from mail.jlokier.co.uk ([81.29.64.88]:56719 "EHLO mail.jlokier.co.uk") by vger.kernel.org with ESMTP id S263580AbTIHVMv (ORCPT ); Mon, 8 Sep 2003 17:12:51 -0400 Date: Mon, 8 Sep 2003 22:12:34 +0100 From: Jamie Lokier To: Hua Zhong Cc: "'Linux Kernel Mailing List'" Subject: Re: THREAD_GROUP and linux thread Message-ID: <20030908211234.GA28109@mail.jlokier.co.uk> References: <127101c3764c$6990df80$ca41cb3f@amer.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <127101c3764c$6990df80$ca41cb3f@amer.cisco.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 672 Lines: 19 Hua Zhong wrote: > but I am just wondering if I could just change the kernel to treat > CLONE_VM the same way as CLONE_THREAD which is a much simpler change. No. There are a good many programs which use CLONE_VM without CLONE_THREAD, and I'm sure they will be surprised to find signals suddenly being shared, which is implied by CLONE_THREAD. > 2. Which version of pthread uses the CLONE_THREAD flag? NPTL. Enjoy, -- Jamie - 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/