[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACVXFVN2njbRR1y6eHZDHwTzsZVo+gi7mJwcZ-eqX=ffdc8-Sw@mail.gmail.com>
Date: Tue, 12 May 2015 16:55:36 +0800
From: Ming Lei <ming.lei@...onical.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dave Kleikamp <dave.kleikamp@...cle.com>,
Jens Axboe <axboe@...nel.dk>, Zach Brown <zab@...bo.net>,
Maxim Patlasov <mpatlasov@...allels.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v3 3/4] block: loop: use kthread_work
On Tue, May 12, 2015 at 3:25 PM, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, May 11, 2015 at 09:12:56PM +0800, Ming Lei wrote:
>> For non-AIO case, single thread has been used for long long time,
>> and it was just converted to work in v4.0, which has caused performance
>> regression for fedora live booting already. In discussion[1], even though
>> submitting I/O via work concurrently can improve random IO throughput,
>> meantime it may hurt sequential IO performance, so maybe better to restore
>> to single thread behaviour.
>
> Then justify the change based on the non-aio use case and document that
> in the changelog.
OK, will add that in v4.
Thanks,
Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists