On Fri, Jul 14, 2017 at 08:54:07AM +0200, Greg KH wrote:
> On Thu, Jul 13, 2017 at 03:24:02PM -0400, Ben Guthro wrote:
> > On Tue, Jul 11, 2017 at 5:55 AM, Greg KH wrote:
> > > On Tue, Jul 11, 2017 at 10:30:14AM +0200, Ingo Molnar wrote:
> > >>
> > >> * Ben Guthro wrote:
> > >>
> > >> > > If peop
On Thu, Jul 13, 2017 at 03:24:02PM -0400, Ben Guthro wrote:
> On Tue, Jul 11, 2017 at 5:55 AM, Greg KH wrote:
> > On Tue, Jul 11, 2017 at 10:30:14AM +0200, Ingo Molnar wrote:
> >>
> >> * Ben Guthro wrote:
> >>
> >> > > If people have experience with these in the "enterprise" distros, or
> >> > >
On Tue, Jul 11, 2017 at 5:55 AM, Greg KH wrote:
> On Tue, Jul 11, 2017 at 10:30:14AM +0200, Ingo Molnar wrote:
>>
>> * Ben Guthro wrote:
>>
>> > > If people have experience with these in the "enterprise" distros, or any
>> > > other
>> > > tree, and want to provide me with backported, and tested
On Tue, Jul 11, 2017 at 10:30:14AM +0200, Ingo Molnar wrote:
>
> * Ben Guthro wrote:
>
> > > If people have experience with these in the "enterprise" distros, or any
> > > other
> > > tree, and want to provide me with backported, and tested, patches, I'll
> > > be
> > > glad to consider them
* Ben Guthro wrote:
> > If people have experience with these in the "enterprise" distros, or any
> > other
> > tree, and want to provide me with backported, and tested, patches, I'll be
> > glad to consider them for stable kernels.
> >
> > thanks,
> >
> > greg k-h
>
> I tried to do a simple
On Mon, Jul 10, 2017 at 11:26 AM, Greg KH wrote:
> On Mon, Jul 10, 2017 at 11:25:32AM +0200, Peter Zijlstra wrote:
>> On Fri, Jul 07, 2017 at 04:55:27PM -0400, Ben Guthro wrote:
>>
>> > Apologies on the delay - it took a bit to get the machines, to run the
>> > test.
>> >
>> > I am happy to repor
On Mon, Jul 10, 2017 at 11:25:32AM +0200, Peter Zijlstra wrote:
> On Fri, Jul 07, 2017 at 04:55:27PM -0400, Ben Guthro wrote:
>
> > Apologies on the delay - it took a bit to get the machines, to run the test.
> >
> > I am happy to report that the kernel at 1ad3aaf3fcd2, seems to regain
> > perfor
On Fri, Jul 07, 2017 at 04:55:27PM -0400, Ben Guthro wrote:
> Apologies on the delay - it took a bit to get the machines, to run the test.
>
> I am happy to report that the kernel at 1ad3aaf3fcd2, seems to regain
> performance loss from 1b568f0aab, in our test environment.
Excellent.
> Since 4.
On Wed, Jul 5, 2017 at 12:48 PM, Peter Zijlstra wrote:
> On Wed, Jul 05, 2017 at 11:42:46AM -0400, Ben Guthro wrote:
>> Hello,
>>
>> I've been in the process of updating our kernel in our appliance VM
>> from an old LTS kernel (4.1.y) to something a bit more modern (4.9.y)
>> - and ran into a perf
On Wed, Jul 05, 2017 at 11:42:46AM -0400, Ben Guthro wrote:
> Hello,
>
> I've been in the process of updating our kernel in our appliance VM
> from an old LTS kernel (4.1.y) to something a bit more modern (4.9.y)
> - and ran into a performance regression, when our QA team was running
> some regres
Hello,
I've been in the process of updating our kernel in our appliance VM
from an old LTS kernel (4.1.y) to something a bit more modern (4.9.y)
- and ran into a performance regression, when our QA team was running
some regression suites.
I bisect this behavior to the following commit, introduce
11 matches
Mail list logo