Subject: Re: Doubt about scheduler
From: Mike Galbraith <efault@gmx.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: =?ISO-8859-1?Q?Ra=FAl?= Baena <raul_baena@ya.com>, jonathan@jonmasters.org,
       linux-kernel@vger.kernel.org
In-Reply-To: <440AE7E3.4060500@yahoo.com.au>
References: <4407584A.60301@ya.com>
	 <35fb2e590603032233i7302162do553ba61674cc8e50@mail.gmail.com>
	 <440AE3F3.3090404@ya.com>  <440AE7E3.4060500@yahoo.com.au>
Content-Type: text/plain; charset=utf-8
Date: Sun, 05 Mar 2006 22:27:34 +0100
Message-Id: <1141594054.7710.18.camel@homer>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 963
Lines: 23

On Mon, 2006-03-06 at 00:30 +1100, Nick Piggin wrote:
> Raúl Baena wrote:
> > Thank you very much Jon. But I think I haven´t explained very well.
> > 
> > I know that now the prio_array and runqueues structs aren´t accesible 
> > for modules, but in the 2.6.5 version they were. I would like to know 
> > the reason, why before they were accesible and now they don´t? If you 
> > could answer me, it would be great.
> 
> I don't remember them being available in 2.6.5... but as to why they
> aren't available now: it is much cleaner this way. It even benefits
> you because now nobody will break your module when they change the
> data structure.

I can't recall having ever seen these exposed.. by Ingo.

	-Mike 

-
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/