> Il giorno 19 apr 2017, alle ore 07:33, Paolo Valente
> ha scritto:
>
>>
>> Il giorno 18 apr 2017, alle ore 09:04, Tejun Heo ha
>> scritto:
>>
>> Hello, Paolo.
>>
>> On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
>>> could you
> Il giorno 19 apr 2017, alle ore 07:33, Paolo Valente
> ha scritto:
>
>>
>> Il giorno 18 apr 2017, alle ore 09:04, Tejun Heo ha
>> scritto:
>>
>> Hello, Paolo.
>>
>> On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
>>> could you elaborate a bit more on this? I mean,
> Il giorno 18 apr 2017, alle ore 09:04, Tejun Heo ha scritto:
>
> Hello, Paolo.
>
> On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
>> could you elaborate a bit more on this? I mean, cgroups support has
>> been in BFQ (and CFQ) for almost ten years, perfectly
> Il giorno 18 apr 2017, alle ore 09:04, Tejun Heo ha scritto:
>
> Hello, Paolo.
>
> On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
>> could you elaborate a bit more on this? I mean, cgroups support has
>> been in BFQ (and CFQ) for almost ten years, perfectly working as far
>>
Hello, Paolo.
On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
> could you elaborate a bit more on this? I mean, cgroups support has
> been in BFQ (and CFQ) for almost ten years, perfectly working as far
> as I know. Of course it is perfectly working in terms of I/O and not
> of
Hello, Paolo.
On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote:
> could you elaborate a bit more on this? I mean, cgroups support has
> been in BFQ (and CFQ) for almost ten years, perfectly working as far
> as I know. Of course it is perfectly working in terms of I/O and not
> of
Hi Arianna,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.11-rc6 next-20170412]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Arianna,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.11-rc6 next-20170412]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
> Il giorno 11 apr 2017, alle ore 23:47, Tejun Heo ha scritto:
>
> Hello,
>
> On Tue, Apr 11, 2017 at 03:43:01PM +0200, Paolo Valente wrote:
>> From: Arianna Avanzini
>>
>> Add complete support for full hierarchical scheduling, with a cgroups
>>
> Il giorno 11 apr 2017, alle ore 23:47, Tejun Heo ha scritto:
>
> Hello,
>
> On Tue, Apr 11, 2017 at 03:43:01PM +0200, Paolo Valente wrote:
>> From: Arianna Avanzini
>>
>> Add complete support for full hierarchical scheduling, with a cgroups
>> interface. Full hierarchical scheduling is
Hello,
On Tue, Apr 11, 2017 at 03:43:01PM +0200, Paolo Valente wrote:
> From: Arianna Avanzini
>
> Add complete support for full hierarchical scheduling, with a cgroups
> interface. Full hierarchical scheduling is implemented through the
> 'entity' abstraction: both
Hello,
On Tue, Apr 11, 2017 at 03:43:01PM +0200, Paolo Valente wrote:
> From: Arianna Avanzini
>
> Add complete support for full hierarchical scheduling, with a cgroups
> interface. Full hierarchical scheduling is implemented through the
> 'entity' abstraction: both bfq_queues, i.e., the
From: Arianna Avanzini
Add complete support for full hierarchical scheduling, with a cgroups
interface. Full hierarchical scheduling is implemented through the
'entity' abstraction: both bfq_queues, i.e., the internal BFQ queues
associated with processes, and groups
From: Arianna Avanzini
Add complete support for full hierarchical scheduling, with a cgroups
interface. Full hierarchical scheduling is implemented through the
'entity' abstraction: both bfq_queues, i.e., the internal BFQ queues
associated with processes, and groups are represented in general by
14 matches
Mail list logo