linux-kernel - RE: Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.22

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5FD5754DDBA0B1499B5A0B4BB54194850164B1F6@fmsmsx411.amr.corp.intel.com>
Date:	Sun, 15 Jul 2007 10:47:51 -0700
From:	"Li, Tong N" <tong.n.li@...el.com>
To:	"Giuseppe Bilotta" <giuseppe.bilotta@...il.com>,
	<linux-kernel@...r.kernel.org>
Subject: RE:  Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for  2.6.22

> On Thursday 12 July 2007 00:17, Al Boldi wrote:
> 
> > Peter Williams wrote:
> >>
> >> Probably the last one now that CFS is in the main line :-(.
> >
> > What do you mean?  A pluggable scheduler framework is indispensible
even
> in
> > the presence of CFS or SD.
> 
> Indeed, and I hope it gets merged, giving people the chance to test
out
> different schedulers easily, without having to do patching,
de-patching,
> re-patching and blah blah blah.
> 

Yes, such a framework would be invaluable, especially given that
scheduling often has conflicting goals and different workloads have
different requirements. No single solution fits all.

> But somehow I doubt it'll get merged now. My bet is that it won't even
be
> taken into consideration, for the same reasons that ultimately drove
Con
> Kolivas to giving up on development of SD. And if it's so, chances are
> people will get tired of trying to get it merged. :/
> 
> >> A patch for 2.6.22 is available at:
> >>
> >> <http://downloads.sourceforge.net/cpuse/plugsched-6.5.1-for-
> 2.6.22.patch>
> >>
> >> Very Brief Documentation:
> >>
> >> You can select a default scheduler at kernel build time.  If you
wish
> to
> >> boot with a scheduler other than the default it can be selected at
boot
> >> time by adding:
> >>
> >> cpusched=<scheduler>
> >>
> >> to the boot command line where <scheduler> is one of: ingosched,
> >> ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr,
spa_ebs
> >> or zaphod.  If you don't change the default when you build the
kernel
> >> the default scheduler will be ingosched (which is the normal
scheduler).
> >
> > Can't PlugSched include CFS and SD?
> 
> If I read the announcement correctly, those are the ones referred to
as
> 'ingosched' and 'staircase' :)
> 
> --
> Giuseppe "Oblomov" Bilotta
> 
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/