On Wed, Oct 05, 2016 at 05:56:16PM -0500, Babu Moger wrote:
> Dave, Gentle reminder to review this patch. Thanks
No need to ping Dave.
It is in patchwork and he will review the patch eventually.
Sam
On Wed, Oct 05, 2016 at 05:56:16PM -0500, Babu Moger wrote:
> Dave, Gentle reminder to review this patch. Thanks
No need to ping Dave.
It is in patchwork and he will review the patch eventually.
Sam
Dave, Gentle reminder to review this patch. Thanks
On 9/30/2016 12:19 AM, David Miller wrote:
From: Babu Moger
Date: Thu, 29 Sep 2016 08:53:24 -0500
On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
This new
Dave, Gentle reminder to review this patch. Thanks
On 9/30/2016 12:19 AM, David Miller wrote:
From: Babu Moger
Date: Thu, 29 Sep 2016 08:53:24 -0500
On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
This new config parameter limits the
From: Babu Moger
Date: Thu, 29 Sep 2016 08:53:24 -0500
>
> On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
>> On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
>>> This new config parameter limits the space used for "Lock debugging:
>>> prove locking correctness" by
From: Babu Moger
Date: Thu, 29 Sep 2016 08:53:24 -0500
>
> On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
>> On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
>>> This new config parameter limits the space used for "Lock debugging:
>>> prove locking correctness" by about 4MB. The current
On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
This new config parameter limits the space used for "Lock debugging:
prove locking correctness" by about 4MB. The current sparc systems have
the limitation of 32MB size for kernel size
On 9/28/2016 3:39 AM, Peter Zijlstra wrote:
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
This new config parameter limits the space used for "Lock debugging:
prove locking correctness" by about 4MB. The current sparc systems have
the limitation of 32MB size for kernel size
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
> This new config parameter limits the space used for "Lock debugging:
> prove locking correctness" by about 4MB. The current sparc systems have
> the limitation of 32MB size for kernel size including .text, .data and
> .bss sections.
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
> This new config parameter limits the space used for "Lock debugging:
> prove locking correctness" by about 4MB. The current sparc systems have
> the limitation of 32MB size for kernel size including .text, .data and
> .bss sections.
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
> This new config parameter limits the space used for "Lock debugging:
> prove locking correctness" by about 4MB. The current sparc systems have
> the limitation of 32MB size for kernel size including .text, .data and
> .bss sections.
On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote:
> This new config parameter limits the space used for "Lock debugging:
> prove locking correctness" by about 4MB. The current sparc systems have
> the limitation of 32MB size for kernel size including .text, .data and
> .bss sections.
This new config parameter limits the space used for "Lock debugging:
prove locking correctness" by about 4MB. The current sparc systems have
the limitation of 32MB size for kernel size including .text, .data and
.bss sections. With PROVE_LOCKING feature, the kernel size could grow
beyond this
This new config parameter limits the space used for "Lock debugging:
prove locking correctness" by about 4MB. The current sparc systems have
the limitation of 32MB size for kernel size including .text, .data and
.bss sections. With PROVE_LOCKING feature, the kernel size could grow
beyond this
14 matches
Mail list logo