Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S316825AbSGBQvW>; Tue, 2 Jul 2002 12:51:22 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S316826AbSGBQvV>; Tue, 2 Jul 2002 12:51:21 -0400
Received: from louise.pinerecords.com ([212.71.160.16]:1796 "EHLO
	louise.pinerecords.com") by vger.kernel.org with ESMTP
	id <S316825AbSGBQvV>; Tue, 2 Jul 2002 12:51:21 -0400
Date: Tue, 2 Jul 2002 18:53:47 +0200
From: Tomas Szepe <szepe@pinerecords.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [OKS] O(1) scheduler in 2.4
Message-ID: <20020702165347.GN19132@louise.pinerecords.com>
References: <20020701234432.GC1697@werewolf.able.es> <Pine.LNX.4.43.0207021802260.29588-100000@cibs9.sns.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.43.0207021802260.29588-100000@cibs9.sns.it>
User-Agent: Mutt/1.4i
X-OS: GNU/Linux 2.4.19-pre10/sparc SMP
X-Uptime: 28 days, 6:44
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 688
Lines: 21

> > >> What's the issue?
> > >
> > >a) We're at 2.4.19-rc1 right now.  It would be horribly
> > >counterproductive to put O(1) in right now.
> >
> > .20-pre1 would be a good start, but my hope is that this reserved for
> > the vm updates from -aa ;).
> 
> If I am not wrong in the AA tree the O(1) scheduler has been merged, so
> there is an opportunity do update booth ;).


... and then hope the thing doesn't turn into a suicide booth.


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