From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933395AbXGLMl3 (ORCPT ); Thu, 12 Jul 2007 08:41:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755362AbXGLMlW (ORCPT ); Thu, 12 Jul 2007 08:41:22 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:42795 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759509AbXGLMlV (ORCPT ); Thu, 12 Jul 2007 08:41:21 -0400 Subject: Re: NPTL From: Peter Zijlstra To: "Ni@m" Cc: davids@webmaster.com, LKML In-Reply-To: References: Content-Type: text/plain Date: Thu, 12 Jul 2007 14:41:18 +0200 Message-Id: <1184244078.20032.48.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2007-07-12 at 15:37 +0300, Ni@m wrote: > So I can say that in linux 'thread' == 'process'? No, a process also contains an address space. > Is kernel routine 'kthread' creating a process? No, that is creating a schedule unit (task) without an address space. > I'm just thinking on this subject: if to create 'real threads' - will > it increase performance? Should I ever think in this way? > When I say 'real thread' - I mean the thread that doen't switch > context when it's starting to run. Surely you need some context switch when switching between runnable contexts. BTW, please do _NOT_ top post!