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
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,
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,
> 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
> >> >>
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
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
> 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
> >
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
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
>
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,
10 matches
Mail list logo