On 6/12/19 10:46 PM, Paolo Valente wrote:
>
>> Il giorno 12 giu 2019, alle ore 00:34, Srivatsa S. Bhat
>> ha scritto:
>>
[...]
>>
>> Hi Paolo,
>>
>
> Hi
>
>> Hope you are doing great!
>>
>
> Sort of, thanks :)
>
>> I was wondering if you got a chance to post these patches to LKML for
>> revi
On 6/13/19 1:20 AM, Jan Kara wrote:
> On Wed 12-06-19 12:36:53, Srivatsa S. Bhat wrote:
>>
>> [ Adding Greg to CC ]
>>
>> On 6/12/19 6:04 AM, Jan Kara wrote:
>>> On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> On 5/30/19 3:45 AM, Paolo Valent
On 6/12/19 11:02 PM, Greg Kroah-Hartman wrote:
> On Wed, Jun 12, 2019 at 12:36:53PM -0700, Srivatsa S. Bhat wrote:
>>
>> [ Adding Greg to CC ]
>>
>> On 6/12/19 6:04 AM, Jan Kara wrote:
>>> On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> On 5/
> Il giorno 12 giu 2019, alle ore 00:34, Srivatsa S. Bhat
> ha scritto:
>
> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
>> On 5/30/19 3:45 AM, Paolo Valente wrote:
>>>
> [...]
>>> At any rate, since you pointed out that you are interested in
>>> out-of-the-box performance, let me complete the
On Wed, Jun 12, 2019 at 12:36:53PM -0700, Srivatsa S. Bhat wrote:
>
> [ Adding Greg to CC ]
>
> On 6/12/19 6:04 AM, Jan Kara wrote:
> > On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
> >> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> >>> On 5/30/19 3:45 AM, Paolo Valente wrote:
>
> >> [..
On Wed 12-06-19 12:36:53, Srivatsa S. Bhat wrote:
>
> [ Adding Greg to CC ]
>
> On 6/12/19 6:04 AM, Jan Kara wrote:
> > On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
> >> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> >>> On 5/30/19 3:45 AM, Paolo Valente wrote:
>
> >> [...]
> At any
On 6/12/19 1:36 PM, Srivatsa S. Bhat wrote:
>
> [ Adding Greg to CC ]
>
> On 6/12/19 6:04 AM, Jan Kara wrote:
>> On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
>>> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
On 5/30/19 3:45 AM, Paolo Valente wrote:
>
>>> [...]
> At any rate, since
[ Adding Greg to CC ]
On 6/12/19 6:04 AM, Jan Kara wrote:
> On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
>> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
>>> On 5/30/19 3:45 AM, Paolo Valente wrote:
>> [...]
At any rate, since you pointed out that you are interested in
out-of-t
On Tue 11-06-19 15:34:48, Srivatsa S. Bhat wrote:
> On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> > On 5/30/19 3:45 AM, Paolo Valente wrote:
> >>
> [...]
> >> At any rate, since you pointed out that you are interested in
> >> out-of-the-box performance, let me complete the context: in case
> >> low
On 6/2/19 12:04 AM, Srivatsa S. Bhat wrote:
> On 5/30/19 3:45 AM, Paolo Valente wrote:
>>
[...]
>> At any rate, since you pointed out that you are interested in
>> out-of-the-box performance, let me complete the context: in case
>> low_latency is left set, one gets, in return for this 12% loss,
>>
On 5/30/19 3:45 AM, Paolo Valente wrote:
>
>
>> Il giorno 30 mag 2019, alle ore 10:29, Srivatsa S. Bhat
>> ha scritto:
>>
[...]
>>
>> Your fix held up well under my testing :)
>>
>
> Great!
>
>> As for throughput, with low_latency = 1, I get around 1.4 MB/s with
>> bfq (vs 1.6 MB/s with mq-de
> Il giorno 30 mag 2019, alle ore 10:29, Srivatsa S. Bhat
> ha scritto:
>
> On 5/29/19 12:41 AM, Paolo Valente wrote:
>>
>>
>>> Il giorno 29 mag 2019, alle ore 03:09, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> On 5/23/19 11:51 PM, Paolo Valente wrote:
> Il giorno 24 mag 2019, alle
On 5/23/19 4:32 PM, Srivatsa S. Bhat wrote:
> On 5/22/19 7:30 PM, Srivatsa S. Bhat wrote:
>> On 5/22/19 3:54 AM, Paolo Valente wrote:
>>>
>>>
Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
ha scritto:
On 5/22/19 2:09 AM, Paolo Valente wrote:
>
> First, thank y
On 5/29/19 12:41 AM, Paolo Valente wrote:
>
>
>> Il giorno 29 mag 2019, alle ore 03:09, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/23/19 11:51 PM, Paolo Valente wrote:
>>>
Il giorno 24 mag 2019, alle ore 01:43, Srivatsa S. Bhat
ha scritto:
When trying to run multiple dd ta
> Il giorno 29 mag 2019, alle ore 03:09, Srivatsa S. Bhat
> ha scritto:
>
> On 5/23/19 11:51 PM, Paolo Valente wrote:
>>
>>> Il giorno 24 mag 2019, alle ore 01:43, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> When trying to run multiple dd tasks simultaneously, I get the kernel
>>> panic shown
On 5/23/19 11:51 PM, Paolo Valente wrote:
>
>> Il giorno 24 mag 2019, alle ore 01:43, Srivatsa S. Bhat
>> ha scritto:
>>
>> When trying to run multiple dd tasks simultaneously, I get the kernel
>> panic shown below (mainline is fine, without these patches).
>>
>
> Could you please provide me so
> Il giorno 24 mag 2019, alle ore 08:51, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 24 mag 2019, alle ore 01:43, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/23/19 10:22 AM, Paolo Valente wrote:
>>>
Il giorno 23 mag 2019, alle ore 11:19, Paolo Valente
ha scritto:
> Il giorno 24 mag 2019, alle ore 01:43, Srivatsa S. Bhat
> ha scritto:
>
> On 5/23/19 10:22 AM, Paolo Valente wrote:
>>
>>> Il giorno 23 mag 2019, alle ore 11:19, Paolo Valente
>>> ha scritto:
>>>
Il giorno 23 mag 2019, alle ore 04:30, Srivatsa S. Bhat
ha scritto:
> [...
On 5/23/19 10:22 AM, Paolo Valente wrote:
>
>> Il giorno 23 mag 2019, alle ore 11:19, Paolo Valente
>> ha scritto:
>>
>>> Il giorno 23 mag 2019, alle ore 04:30, Srivatsa S. Bhat
>>> ha scritto:
>>>
[...]
>>> Also, I'm very happy to run additional tests or experiments to help
>>> track down thi
On 5/22/19 7:30 PM, Srivatsa S. Bhat wrote:
> On 5/22/19 3:54 AM, Paolo Valente wrote:
>>
>>
>>> Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> On 5/22/19 2:09 AM, Paolo Valente wrote:
First, thank you very much for testing my patches, and, above all, fo
> Il giorno 23 mag 2019, alle ore 11:19, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 23 mag 2019, alle ore 04:30, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/22/19 3:54 AM, Paolo Valente wrote:
>>>
>>>
Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
ha scritto:
>>>
> Il giorno 23 mag 2019, alle ore 04:30, Srivatsa S. Bhat
> ha scritto:
>
> On 5/22/19 3:54 AM, Paolo Valente wrote:
>>
>>
>>> Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> On 5/22/19 2:09 AM, Paolo Valente wrote:
First, thank you very much for
On 5/22/19 3:54 AM, Paolo Valente wrote:
>
>
>> Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/22/19 2:09 AM, Paolo Valente wrote:
>>>
>>> First, thank you very much for testing my patches, and, above all, for
>>> sharing those huge traces!
>>>
>>> According t
> Il giorno 22 mag 2019, alle ore 12:01, Srivatsa S. Bhat
> ha scritto:
>
> On 5/22/19 2:09 AM, Paolo Valente wrote:
>>
>> First, thank you very much for testing my patches, and, above all, for
>> sharing those huge traces!
>>
>> According to the your traces, the residual 20% lower throughpu
On 5/22/19 2:12 AM, Paolo Valente wrote:
>
>> Il giorno 22 mag 2019, alle ore 11:02, Srivatsa S. Bhat
>> ha scritto:
>>
>>
>> Let's continue here on LKML itself.
>
> Just done :)
>
>> The only reason I created the
>> bugzilla entry is to attach the tarball of the traces, assuming
>> that it wo
On 5/22/19 2:09 AM, Paolo Valente wrote:
>
> First, thank you very much for testing my patches, and, above all, for
> sharing those huge traces!
>
> According to the your traces, the residual 20% lower throughput that you
> record is due to the fact that the BFQ injection mechanism takes a few
>
> Il giorno 22 mag 2019, alle ore 11:02, Srivatsa S. Bhat
> ha scritto:
>
> On 5/22/19 1:05 AM, Paolo Valente wrote:
>>
>>
>>> Il giorno 22 mag 2019, alle ore 00:51, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> [ Resending this mail with a dropbox link to the traces (instead
>>> of a file att
> Il giorno 22 mag 2019, alle ore 10:05, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 22 mag 2019, alle ore 00:51, Srivatsa S. Bhat
>> ha scritto:
>>
>> [ Resending this mail with a dropbox link to the traces (instead
>> of a file attachment), since it didn't go through the last time. ]
On 5/22/19 1:05 AM, Paolo Valente wrote:
>
>
>> Il giorno 22 mag 2019, alle ore 00:51, Srivatsa S. Bhat
>> ha scritto:
>>
>> [ Resending this mail with a dropbox link to the traces (instead
>> of a file attachment), since it didn't go through the last time. ]
>>
>> On 5/21/19 10:38 AM, Paolo Va
> Il giorno 22 mag 2019, alle ore 00:51, Srivatsa S. Bhat
> ha scritto:
>
> [ Resending this mail with a dropbox link to the traces (instead
> of a file attachment), since it didn't go through the last time. ]
>
> On 5/21/19 10:38 AM, Paolo Valente wrote:
>>
>>> So, instead of only sending m
[ Resending this mail with a dropbox link to the traces (instead
of a file attachment), since it didn't go through the last time. ]
On 5/21/19 10:38 AM, Paolo Valente wrote:
>
>> So, instead of only sending me a trace, could you please:
>> 1) apply this new patch on top of the one I attached in m
On Tue, May 21, 2019 at 02:19:53PM -0400, Josef Bacik wrote:
> Chris is adding a REQ_ROOT (or something) flag that means don't throttle me
> now,
> but the the blkcg attached to the bio is the one that is responsible for this
> IO. Then for io.latency we'll let the io go through unmolested but it
On Tue, May 21, 2019 at 12:48:14PM -0400, Theodore Ts'o wrote:
> On Mon, May 20, 2019 at 11:15:58AM +0200, Jan Kara wrote:
> > But this makes priority-inversion problems with ext4 journal worse, doesn't
> > it? If we submit journal commit in blkio cgroup of some random process, it
> > may get throt
> Il giorno 21 mag 2019, alle ore 18:21, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 21 mag 2019, alle ore 15:20, Paolo Valente
>> ha scritto:
>>
>>
>>
>>> Il giorno 21 mag 2019, alle ore 13:25, Paolo Valente
>>> ha scritto:
>>>
>>>
>>>
Il giorno 20 mag 2019, alle ore 12:19
On Mon, May 20, 2019 at 11:15:58AM +0200, Jan Kara wrote:
> But this makes priority-inversion problems with ext4 journal worse, doesn't
> it? If we submit journal commit in blkio cgroup of some random process, it
> may get throttled which then effectively blocks the whole filesystem. Or do
> you wa
On Tue, May 21, 2019 at 11:10:26AM +0200, Jan Kara wrote:
> > [root@localhost tmp]# dd if=/dev/zero of=/root/test.img bs=512 count=1
> > oflag=dsync
>
> Yes and that's expected. It just shows how inefficient small synchronous IO
> is. Look, dd(1) writes 512-bytes. From FS point of view we hav
> Il giorno 21 mag 2019, alle ore 15:20, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 21 mag 2019, alle ore 13:25, Paolo Valente
>> ha scritto:
>>
>>
>>
>>> Il giorno 20 mag 2019, alle ore 12:19, Paolo Valente
>>> ha scritto:
>>>
>>>
>>>
Il giorno 18 mag 2019, alle ore 22:50
> Il giorno 21 mag 2019, alle ore 13:25, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 20 mag 2019, alle ore 12:19, Paolo Valente
>> ha scritto:
>>
>>
>>
>>> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> On 5/18/19 11:39 AM, Paolo Valente wrote:
>>>
> Il giorno 20 mag 2019, alle ore 12:19, Paolo Valente
> ha scritto:
>
>
>
>> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/18/19 11:39 AM, Paolo Valente wrote:
>>> I've addressed these issues in my last batch of improvements for BFQ,
>>> which landed i
On Tue 21-05-19 08:23:05, Paolo Valente wrote:
> > Il giorno 21 mag 2019, alle ore 00:45, Srivatsa S. Bhat
> > ha scritto:
> >
> > On 5/20/19 3:19 AM, Paolo Valente wrote:
> >>
> >>
> >>> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
> >>> ha scritto:
> >>>
> >>> On 5/18/19 11:39
On Mon, May 20, 2019 at 12:38:32PM +0200, Paolo Valente wrote:
...
> > I was considering adding support so that if userspace calls fsync(2)
> > or fdatasync(2), to attach the process's CSS to the transaction, and
> > then charge all of the journal metadata writes the process's CSS. If
> > there ar
On 5/20/19 11:23 PM, Paolo Valente wrote:
>
>
>> Il giorno 21 mag 2019, alle ore 00:45, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/20/19 3:19 AM, Paolo Valente wrote:
>>>
>>>
Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
ha scritto:
On 5/18/19 11:39 AM, Paolo Val
> Il giorno 21 mag 2019, alle ore 00:45, Srivatsa S. Bhat
> ha scritto:
>
> On 5/20/19 3:19 AM, Paolo Valente wrote:
>>
>>
>>> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
>>> ha scritto:
>>>
>>> On 5/18/19 11:39 AM, Paolo Valente wrote:
I've addressed these issues in my l
On 5/20/19 3:19 AM, Paolo Valente wrote:
>
>
>> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
>> ha scritto:
>>
>> On 5/18/19 11:39 AM, Paolo Valente wrote:
>>> I've addressed these issues in my last batch of improvements for BFQ,
>>> which landed in the upcoming 5.2. If you give it a
> Il giorno 20 mag 2019, alle ore 11:15, Jan Kara ha scritto:
>
> On Sat 18-05-19 15:28:47, Theodore Ts'o wrote:
>> On Sat, May 18, 2019 at 08:39:54PM +0200, Paolo Valente wrote:
>>> I've addressed these issues in my last batch of improvements for
>>> BFQ, which landed in the upcoming 5.2. If y
> Il giorno 18 mag 2019, alle ore 21:28, Theodore Ts'o ha
> scritto:
>
> On Sat, May 18, 2019 at 08:39:54PM +0200, Paolo Valente wrote:
>> I've addressed these issues in my last batch of improvements for
>> BFQ, which landed in the upcoming 5.2. If you give it a try, and
>> still see the probl
> Il giorno 18 mag 2019, alle ore 22:50, Srivatsa S. Bhat
> ha scritto:
>
> On 5/18/19 11:39 AM, Paolo Valente wrote:
>> I've addressed these issues in my last batch of improvements for BFQ,
>> which landed in the upcoming 5.2. If you give it a try, and still see
>> the problem, then I'll be g
On Sat 18-05-19 15:28:47, Theodore Ts'o wrote:
> On Sat, May 18, 2019 at 08:39:54PM +0200, Paolo Valente wrote:
> > I've addressed these issues in my last batch of improvements for
> > BFQ, which landed in the upcoming 5.2. If you give it a try, and
> > still see the problem, then I'll be glad to r
On 5/18/19 11:39 AM, Paolo Valente wrote:
> I've addressed these issues in my last batch of improvements for BFQ,
> which landed in the upcoming 5.2. If you give it a try, and still see
> the problem, then I'll be glad to reproduce it, and hopefully fix it
> for you.
>
Hi Paolo,
Thank you for loo
On Sat, May 18, 2019 at 08:39:54PM +0200, Paolo Valente wrote:
> I've addressed these issues in my last batch of improvements for
> BFQ, which landed in the upcoming 5.2. If you give it a try, and
> still see the problem, then I'll be glad to reproduce it, and
> hopefully fix it for you.
Hi Paolo,
I've addressed these issues in my last batch of improvements for BFQ, which
landed in the upcoming 5.2. If you give it a try, and still see the problem,
then I'll be glad to reproduce it, and hopefully fix it for you.
Thanks,
Paolo
> Il giorno 18 mag 2019, alle ore 00:16, Srivatsa S. Bhat
> h
Hi,
One of my colleagues noticed upto 10x - 30x drop in I/O throughput
running the following command, with the CFQ I/O scheduler:
dd if=/dev/zero of=/root/test.img bs=512 count=1 oflags=dsync
Throughput with CFQ: 60 KB/s
Throughput with noop or deadline: 1.5 MB/s - 2 MB/s
I spent some tim
52 matches
Mail list logo
