Date: Sat, 25 Jan 2003 23:20:11 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Robert Watson <rwatson@FreeBSD.ORG>, Gary Jennejohn <garyj@jennejohn.org>, arch@FreeBSD.ORG Subject: Re: New scheduler - Interactivity fixes Message-ID: <Pine.BSF.4.21.0301252309090.89171-100000@InterJet.elischer.org> In-Reply-To: <20030126013746.C7994-100000@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Jan 2003, Jeff Roberson wrote: > > On Sat, 25 Jan 2003, Julian Elischer wrote: > > > I think that the option should be set up so that no option gives the > > current scheduler. > > We discussed that but that would require adding a #ifndef each time a > scheduler was added. It's less appealing long term. Sorry we didn't > include you on this discussion. I sent requests for feedback on this with > my first arch@ post and eventually ended up directly discussing it with > re. Huh? Did I not indicate an interest? if you mean the post earluer today, then it needs abit more than one day.... I happen to think that what you are doing is good because we need the ability to abstract the scheduler, but 're@' doesn't have any say in this.. it's not an 're' issue. Making thousands of people go and edit their config files is just 'unfriendly'. This is an "arch@" issue and I think that you need to revert this change until it's been discussed in the correct forum. Maybe it's come to the decision that what you have done is corrrect but I suspect that having a default scheduler is more in line with POLA than suddenly having to specify one. The standard proceedure for adding a new "to be standard" feature is: Make the new feature an option, leaving the original as default. Make the old one as a feature as well. Change the default > > Cheers, > Jeff > > > > > > On Sun, 26 Jan 2003, Jeff Roberson wrote: > > > > > In a moment I'm adding some config options to handle this. I sent some > > > mail out to current@ and I'm adding a line to updating. This has all gone > > > through re. You will be required to specify one of SCHED_4BSD or > > > SCHED_ULE (new name for sched_smp) in your config file. I went away from > > > sched_smp because it should be a very effective up scheduler as well. > > > > > > Cheers, > > > Jeff > > > > > > On Sat, 25 Jan 2003, Matthew Dillon wrote: > > > > > > > Jeff, how are you loading your scheduler in? In my tests I just > > > > #if 0'd out sched_4bsd.c and added sched_smp.c to conf/files, but > > > > I think I'm missing something. Is there some way to set the scheduler > > > > at boot time (e.g. sched_4bsd.c vs sched_smp.c)? > > > > > > > > -Matt > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-arch" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-arch" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-arch" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0301252309090.89171-100000>