On 2016-06-18 10:45, Konstantin Khlebnikov wrote:
On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
wrote:
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes
On 2016-06-18 10:45, Konstantin Khlebnikov wrote:
On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
wrote:
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump
On 06/18/16 14:45, Konstantin Khlebnikov wrote:
> On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
> wrote:
>> On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
>>>
>>> I don't like the idea of this patchset.
>>>
>>> All limitations are context dependent and that
On 06/18/16 14:45, Konstantin Khlebnikov wrote:
> On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
> wrote:
>> On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
>>>
>>> I don't like the idea of this patchset.
>>>
>>> All limitations are context dependent and that context changes rapidly.
>>>
On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
wrote:
> On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
>>
>> I don't like the idea of this patchset.
>>
>> All limitations are context dependent and that context changes rapidly.
>> You'll never dump enough
On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
wrote:
> On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
>>
>> I don't like the idea of this patchset.
>>
>> All limitations are context dependent and that context changes rapidly.
>> You'll never dump enough information for predicting
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump enough information for predicting future errors or
investigating reson of errors in past. You could try to
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump enough information for predicting future errors or
investigating reson of errors in past. You could try to
On 06/14/16 19:03, Konstantin Khlebnikov wrote:
> I don't like the idea of this patchset.
>
> All limitations are context dependent and that context changes rapidly.
> You'll never dump enough information for predicting future errors or
> investigating reson of errors in past. You could try to
On 06/14/16 19:03, Konstantin Khlebnikov wrote:
> I don't like the idea of this patchset.
>
> All limitations are context dependent and that context changes rapidly.
> You'll never dump enough information for predicting future errors or
> investigating reson of errors in past. You could try to
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump enough information for predicting future errors or
investigating reson of errors in past. You could try to reproduce all
kernel logic but model always will be
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump enough information for predicting future errors or
investigating reson of errors in past. You could try to reproduce all
kernel logic but model always will be
Hello,
There are many basic ways to control processes, including capabilities,
cgroups and resource limits. However, there are far fewer ways to find out
useful values for the limits, except blind trial and error.
This patch series attempts to fix that by giving at least a nice starting
point
Hello,
There are many basic ways to control processes, including capabilities,
cgroups and resource limits. However, there are far fewer ways to find out
useful values for the limits, except blind trial and error.
This patch series attempts to fix that by giving at least a nice starting
point
14 matches
Mail list logo