Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-23 Thread Julian Elischer
On 22/4/18 9:43 pm, Rick Macklem wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: I decided to start a new thread on current related to SCHED_ULE, since I

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-23 Thread Julian Elischer
On 22/4/18 10:36 pm, Rodney W. Grimes wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: I decided to start a new thread on current related to SCHED_ULE,

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-23 Thread Julian Elischer
On 22/4/18 10:36 pm, Rodney W. Grimes wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: Konstantin Belousov wrote: On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: I decided to start a new thread on current related to SCHED_ULE,

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-22 Thread Rodney W. Grimes
> Konstantin Belousov wrote: > >On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: > >> Konstantin Belousov wrote: > >> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > >> >> I decided to start a new thread on current related to SCHED_ULE, since > >> >> I see > >> >>

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-22 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: >> Konstantin Belousov wrote: >> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: >> >> I decided to start a new thread on current related to SCHED_ULE, since I >> >> see >> >> more than just

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-22 Thread Konstantin Belousov
On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote: > Konstantin Belousov wrote: > >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > >> I decided to start a new thread on current related to SCHED_ULE, since I > >> see > >> more than just performance degradation and on a

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Rodney W. Grimes
> On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > > I decided to start a new thread on current related to SCHED_ULE, since I see > > more than just performance degradation and on a recent current kernel. > > (I cc'd a couple of the people discussing performance problems in > >

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Rick Macklem
Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: >> I decided to start a new thread on current related to SCHED_ULE, since I see >> more than just performance degradation and on a recent current kernel. >> (I cc'd a couple of the people discussing

Re: SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Konstantin Belousov
On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > I decided to start a new thread on current related to SCHED_ULE, since I see > more than just performance degradation and on a recent current kernel. > (I cc'd a couple of the people discussing performance problems in >

SCHED_ULE makes 256Mbyte i386 unusable

2018-04-21 Thread Rick Macklem
I decided to start a new thread on current related to SCHED_ULE, since I see more than just performance degradation and on a recent current kernel. (I cc'd a couple of the people discussing performance problems in freebsd-stable recently under a subject line of "Re: kern.sched.quantum: Creepy,