From owner-freebsd-bugs Thu Jan 10 9:49:33 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from november.debolaz.com (november.debolaz.com [193.71.19.191]) by hub.freebsd.org (Postfix) with ESMTP id C138E37B400; Thu, 10 Jan 2002 09:49:30 -0800 (PST) Received: from amphibic.com (november [193.71.19.191]) by november.debolaz.com (Postfix) with SMTP id E904113602E; Thu, 10 Jan 2002 18:49:25 +0100 (CET) Received: from 62.179.128.205 (proxying for unknown) (SquirrelMail authenticated user debolaz) by webmail.debolaz.com with HTTP; Thu, 10 Jan 2002 18:49:25 +0100 (CET) Message-ID: <54540.62.179.128.205.1010684965.squirrel@webmail.debolaz.com> Date: Thu, 10 Jan 2002 18:49:25 +0100 (CET) Subject: Re: kern/33124: kthread_create doesnt mark kthreads as kthreads. From: "Anders Nor Berle" To: In-Reply-To: References: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: , X-Mailer: SquirrelMail (version 1.2.0 [cvs]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > This is actually kind of bogus. Nobody uses this flag except aio, and aio just sets > the flag, no code actually checks it. P_KTHREAD is a new flag in -current used in a > few places. Unless the submitter has code that actually checks P_KTHREADP and needs > it set for some reason, I would rather see the flag killed. One thing that might be > nice to MFC is changing aio to use kthread_create rather than using its own > home-rolled version. > Well, I do have some code, related to jail, which checks for P_KTHREADP, but if P_KTHREAD becomes available instead, that'll do of course. I was just following what was already there. :) - Anders Nor Berle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message