From owner-freebsd-hackers@FreeBSD.ORG Thu May 5 22:15:45 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E62C416A4CE for ; Thu, 5 May 2005 22:15:45 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6446643D5E for ; Thu, 5 May 2005 22:15:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j45MLCp8002405; Thu, 5 May 2005 16:21:13 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <427A9AD5.6050201@samsco.org> Date: Thu, 05 May 2005 16:14:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Halil Demirezen References: <200505060010.26184.halil@enderunix.org> <427A94C0.1020205@samsco.org> <200505060103.38645.halil@enderunix.org> In-Reply-To: <200505060103.38645.halil@enderunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-hackers@freebsd.org Subject: Re: A bit confused with the sched_4bsd.c code X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 22:15:46 -0000 Halil Demirezen wrote: > On Thursday 05 May 2005 21:48, Scott Long wrote: > >>#define td_kse td_sched > > > Yes that is also a magical case since in the sys/proc.h file, > only a single definition lies; > > struct td_sched; That's called a forward declaration. > > I could not understand anything from this. There is not body of the structure. > Shouldn't there be a definitive structure for td_sched? if there is i really > could not find the body :) > > hmm, what kind of a different matter is this ? :-) td_sched is defined within each scheduler source file. Since the schedulers are mutually exclusive, they don't collide. Scott