Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Feb 2003 15:00:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Feb 2003 15:00:45 -0500 Received: from hera.cwi.nl ([192.16.191.8]:44709 "EHLO hera.cwi.nl") by vger.kernel.org with ESMTP id ; Thu, 6 Feb 2003 15:00:41 -0500 From: Andries.Brouwer@cwi.nl Date: Thu, 6 Feb 2003 21:10:18 +0100 (MET) Message-Id: To: linux-kernel@vger.kernel.org Subject: syscall documentation (4) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1231 Lines: 41 The next new page is gettid(2). Comments welcome. Andries aeb@cwi.nl ----------------------------------- GETTID(2) Linux Programmer's Manual GETTID(2) NAME gettid - get thread identification SYNOPSIS #include #include _syscall0(pid_t,gettid) pid_t gettid(void); DESCRIPTION gettid returns the thread ID of the current process. This is equal to the process ID (as returned by getpid(2)), unless the process is part of a thread group (created by specifying the CLONE_THREAD flag to the clone(2) system call). All processes in the same thread group have the same PID, but each one has a unique TID. CONFORMING TO gettid is Linux specific and should not be used in pro? grams that are intended to be portable. SEE ALSO getpid(2), clone(2), fork(2) Linux 2.4.20 2003-02-01 GETTID(2) - 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/