From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 18 15:25:17 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C909016A41B for ; Mon, 18 Feb 2008 15:25:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 6D31D13C4CC for ; Mon, 18 Feb 2008 15:25:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 6ED1243F63E for ; Mon, 18 Feb 2008 17:25:15 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Um6pVOlAC4Y0 for ; Mon, 18 Feb 2008 17:25:15 +0200 (EET) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 0B70B43D614 for ; Mon, 18 Feb 2008 17:25:14 +0200 (EET) Message-ID: <47B9A359.9080502@icyb.net.ua> Date: Mon, 18 Feb 2008 17:25:13 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20080123) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: sched_ule: roundrobin_callout replacement ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 15:25:17 -0000 I see that sched_4bsd has a NOP callout with a purpose of forcing a context switch (via softclock), so that something like a preemption could happen (e.g. for threads in a tight calculation loop). What serves the similar purpose for sched_ule? Or, how sched_ule deals with the issue without needing softclock's help? -- Andriy Gapon