Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 19 Jun 2002 18:39:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 19 Jun 2002 18:39:18 -0400 Received: from mx1.elte.hu ([157.181.1.137]:28800 "HELO mx1.elte.hu") by vger.kernel.org with SMTP id ; Wed, 19 Jun 2002 18:39:17 -0400 Date: Thu, 20 Jun 2002 00:37:17 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Bill Davidsen Cc: Rusty Russell , Linux Kernel Mailing List Subject: Re: Question about sched_yield() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1009 Lines: 25 On Wed, 19 Jun 2002, Bill Davidsen wrote: > [...] I'd like to see threads of a single process be able to get, use, > and share a timeslice before some cpu hog comes in and get his > timeslice. there is no such concept as 'threads of a single process' in Linux, and this is not just a naming difference. In Linux threads are threads, and whether they share the same set of pagetables or not is secondary to the kernel. (there are lots of other resources they might or might not share between each other.) the OS where processes 'own' threads, where the process is a container, where this concept is pretty much the only meaningful multiprogramming concept, and where the kernel API is separated into per-thread and per-process parts is not called Linux. Ingo - 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/