Il 06/05/2016 22:20, Paolo Valente ha scritto:
...
I can now confirm that, because of a little bug, a fraction ranging
from one third to half of the writeback bios for the writer is wrongly
associated with the root group. I'm sending a bugfix.
I'm retesting BFQ after this blk fix. If I underst
Il giorno 25/apr/2016, alle ore 22:30, Paolo ha
scritto:
> Il 25/04/2016 21:24, Tejun Heo ha scritto:
>> Hello, Paolo.
>>
>
> Hi
>
>> On Sat, Apr 23, 2016 at 09:07:47AM +0200, Paolo Valente wrote:
>>> There is certainly something I don’t know here, because I don’t
>>> understand why there is
Il 25/04/2016 21:24, Tejun Heo ha scritto:
Hello, Paolo.
Hi
On Sat, Apr 23, 2016 at 09:07:47AM +0200, Paolo Valente wrote:
There is certainly something I don’t know here, because I don’t
understand why there is also a workqueue containing root-group I/O
all the time, if the only process doi
Hello, Paolo.
On Sat, Apr 23, 2016 at 09:07:47AM +0200, Paolo Valente wrote:
> There is certainly something I don’t know here, because I don’t
> understand why there is also a workqueue containing root-group I/O
> all the time, if the only process doing I/O belongs to a different
> (sub)group.
Hm
Il giorno 22/apr/2016, alle ore 21:32, Tejun Heo ha scritto:
> Hello, Paolo.
>
> On Fri, Apr 22, 2016 at 09:05:14PM +0200, Paolo Valente wrote:
>>> Ah, right, I was confused. cic is always associated with the task and
>>> yes a writeback worker can trigger blkcg changed events frequently as
>>
Hello, Paolo.
On Fri, Apr 22, 2016 at 09:05:14PM +0200, Paolo Valente wrote:
> > Ah, right, I was confused. cic is always associated with the task and
> > yes a writeback worker can trigger blkcg changed events frequently as
> > it walks through different cgroups. Is this an issue?
>
> That’s e
Il giorno 22/apr/2016, alle ore 20:41, Tejun Heo ha scritto:
> Hello, Paolo.
>
> On Fri, Apr 22, 2016 at 08:19:47PM +0200, Paolo Valente wrote:
>>> So, a kworker would jump through different workqueues and issue IOs
>>> for different writeback domains and the context can't be tied to the
>>> is
Hello, Paolo.
On Fri, Apr 22, 2016 at 08:19:47PM +0200, Paolo Valente wrote:
> > So, a kworker would jump through different workqueues and issue IOs
> > for different writeback domains and the context can't be tied to the
> > issuing task. The cgroup membership should be determined directly
> > f
Il giorno 22/apr/2016, alle ore 20:13, Tejun Heo ha scritto:
> Hello, Paolo.
>
> On Wed, Apr 20, 2016 at 11:32:23AM +0200, Paolo wrote:
>> This malfunction seems related to a blkcg behavior that I did not
>> expect: the sequential writer changes group continuously. It moves
>> from the root gro
Hello, Paolo.
On Wed, Apr 20, 2016 at 11:32:23AM +0200, Paolo wrote:
> This malfunction seems related to a blkcg behavior that I did not
> expect: the sequential writer changes group continuously. It moves
> from the root group to its correct group, and back. Here is the
> output of
>
> egrep 'in
[Resending in plain text]
Il 11/02/2016 23:28, Tejun Heo ha scritto:
Hello, > > On Mon, Feb 01, 2016 at 11:12:46PM +0100, Paolo Valente wrote: >>
From: Arianna Avanzini >> >> Complete
support for full hierarchical scheduling, with a cgroups >> interface.
The name of the added policy is bfq.
Hello, again.
I forgot to cc the source code for the following.
> A-2. test-rawio.c $DEV 8 16
It's a simple program which issues random IOs to the raw device. The
above will issue 16 concurrent 4k IOs.
Thanks.
--
tejun
#define _GNU_SOURCE
#define _FILE_OFFSET_BITS 64
#include
#include
#in
Hello,
On Wed, Feb 17, 2016 at 10:07:16AM +0100, Paolo Valente wrote:
> > * How's writeback handled?
>
> If I understood correctly your question, then the answer is that
> there is no special/automatic handling of writeback queues. Thus,
> unless the user explicitly inserts flushing threads in so
Il giorno 11/feb/2016, alle ore 23:28, Tejun Heo ha scritto:
> Hello,
>
> On Mon, Feb 01, 2016 at 11:12:46PM +0100, Paolo Valente wrote:
>> From: Arianna Avanzini
>>
>> Complete support for full hierarchical scheduling, with a cgroups
>> interface. The name of the added policy is bfq.
>>
>>
Hello,
On Mon, Feb 01, 2016 at 11:12:46PM +0100, Paolo Valente wrote:
> From: Arianna Avanzini
>
> Complete support for full hierarchical scheduling, with a cgroups
> interface. The name of the added policy is bfq.
>
> Weights can be assigned explicitly to groups and processes through the
> cgr
From: Arianna Avanzini
Complete support for full hierarchical scheduling, with a cgroups
interface. The name of the added policy is bfq.
Weights can be assigned explicitly to groups and processes through the
cgroups interface, differently from what happens, for single
processes, if the cgroups i
16 matches
Mail list logo