From owner-freebsd-current Fri Jun 14 0: 1: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 0792B37B437 for ; Fri, 14 Jun 2002 00:00:20 -0700 (PDT) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020614070016.DCOE2751.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Fri, 14 Jun 2002 07:00:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA97807 for ; Thu, 13 Jun 2002 23:55:36 -0700 (PDT) Date: Thu, 13 Jun 2002 23:55:36 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: KSE changes to ps Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So the question is: what information can PS show for a KSE threaded process? I have been thinking of: Certainly the first thing to decide it WHAT there is to show.. threads that are in userspace are not visible to ps, or for that matter the kernel, as teh Userland thread scheduler may switch between them without notifying the kernel. Only threads blocked in the kernel can show any information other than "running" For those in the userland there is only the information in the associated kse , and priority info from the thread is available. so for a process you can show: process stuff (e.g. uid, pid, ppid) kseg stuff (e.g. nice value, number runnable threads) kse stuff(e.g. RUNNING @ priority 32 on cpu0) kse stuff(e.g. RUNNING @ priority 31 on cpu1) runnable threads e.g. thread runnable priority 33 thread runnable priority 35 thread runnable priority 37 sleeping threads e.g. thread waiting at Mutex net1 prio 33 thread sleeping at "biord" prio 31 kseg stuff (for next kseg) ... anyone have thoughts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message