Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Doug Barton
On 12/16/2011 14:59, Luigi Rizzo wrote: > It really looks much easier than i thought initially. Awesome! -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Luigi Rizzo
On Fri, Dec 16, 2011 at 01:51:26PM -0800, Doug Barton wrote: > On 12/16/2011 13:40, Michel Talon wrote: > > Adrian Chadd said: > > > > > >> Hi all, > >> > >> Can someone load a kernel module dynamically at boot-time? > >> > >> Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Doug Barton
On 12/16/2011 14:16, Michel Talon wrote: > Of course, you are perfectly right., and i had misunderstood Adrian's > post. Happens to the best of us. :) > But if the problem is only to change scheduler by rebooting, i think > it is no more expensive to compile a kernel with the other scheduler. >

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Michel Talon
Le 16 déc. 2011 à 22:51, Doug Barton a écrit : > On 12/16/2011 13:40, Michel Talon wrote: >> Adrian Chadd said: >> >> >>> Hi all, >>> >>> Can someone load a kernel module dynamically at boot-time? >>> >>> Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at >>> boot-time, so th

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Doug Barton
On 12/16/2011 13:40, Michel Talon wrote: > Adrian Chadd said: > > >> Hi all, >> >> Can someone load a kernel module dynamically at boot-time? >> >> Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at >> boot-time, so the user can just change by rebooting? >> >> That may be an a

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Michel Talon
Adrian Chadd said: > Hi all, > > Can someone load a kernel module dynamically at boot-time? > > Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at > boot-time, so the user can just change by rebooting? > > That may be an acceptable solution for now. As Luigi explained, the pro

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Doug Barton
On 12/16/2011 12:53, Adrian Chadd wrote: > Hi all, > > Can someone load a kernel module dynamically at boot-time? > > Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at > boot-time, so the user can just change by rebooting? > > That may be an acceptable solution for now. That, o

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Adrian Chadd
Hi all, Can someone load a kernel module dynamically at boot-time? Ie, instead of compiling it in, can 4bsd/ule be loaded as a KLD at boot-time, so the user can just change by rebooting? That may be an acceptable solution for now. Adrian ___ freebsd-

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Luigi Rizzo
On Fri, Dec 16, 2011 at 11:46:35AM +0100, Stefan Esser wrote: > Am 16.12.2011 09:11, schrieb Luigi Rizzo: > > The interesting part is probably the definition of the methods that > > schedulers should implement (see struct _sched_interface ). > > > > The switch from one scheduler to another was imp

Re: switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Stefan Esser
Am 16.12.2011 09:11, schrieb Luigi Rizzo: > The interesting part is probably the definition of the methods that > schedulers should implement (see struct _sched_interface ). > > The switch from one scheduler to another was implemented with a > sysctl. This calls the sched_move() method of the curr

switching schedulers (Re: SCHED_ULE should not be the default)

2011-12-16 Thread Luigi Rizzo
On Fri, Dec 16, 2011 at 03:11:43AM +0100, C. P. Ghost wrote: > On Thu, Dec 15, 2011 at 10:44 AM, Tom Evans wrote: > > Real time scheduler changing would be insane! I was thinking that > > both/any/all schedulers could be compiled into the kernel, and the > > choice of which one to use becomes a bo