public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin M. Forbes" <jforbes@fedoraproject.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-kernel@vger.kernel.org, Jeff Moyer <jmoyer@redhat.com>,
	Tejun Heo <tj@kernel.org>, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/2] block: loop: fix stacked loop and performance regression
Date: Tue, 05 May 2015 14:01:05 -0500	[thread overview]
Message-ID: <1430852465.11260.1.camel@fedoraproject.org> (raw)
In-Reply-To: <1430826595-5888-1-git-send-email-ming.lei@canonical.com>

On Tue, 2015-05-05 at 19:49 +0800, Ming Lei wrote:
> Hi,
> 
> The 1st patch convers to per-device workqueue because loop devices
> can be stacked.
> 
> The 2nd patch decreases max active works as 16, so that fedora 22's
> boot performance regression can be fixed.
> 
>  drivers/block/loop.c | 30 ++++++++++++++----------------
>  drivers/block/loop.h |  1 +
>  2 files changed, 15 insertions(+), 16 deletions(-)
> 
> 
> Thanks,
> Ming Lei
> 

Tested with Fedora 22 ISOs, these still solve the problem for us.

Tested-by: Justin M. Forbes <jforbes@fedoraproject.org>


      parent reply	other threads:[~2015-05-05 19:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 11:49 [PATCH 0/2] block: loop: fix stacked loop and performance regression Ming Lei
2015-05-05 11:49 ` [PATCH 1/2] block: loop: convert to per-device workqueue Ming Lei
2015-05-05 14:00   ` Tejun Heo
2015-05-26 22:29   ` Dave Kleikamp
2015-05-05 11:49 ` [PATCH 2/2] block: loop: avoiding too many pending per work I/O Ming Lei
2015-05-05 13:59   ` Tejun Heo
2015-05-05 14:46     ` Ming Lei
2015-05-05 16:55       ` Tejun Heo
2015-05-06  3:14         ` Ming Lei
2015-05-06  5:17           ` Ming Lei
2015-05-06  7:36             ` Christoph Hellwig
2015-05-06 11:43               ` Ming Lei
2015-05-22 12:36   ` Josh Boyer
2015-05-22 13:32     ` Ming Lei
2015-05-05 19:01 ` Justin M. Forbes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1430852465.11260.1.camel@fedoraproject.org \
    --to=jforbes@fedoraproject.org \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox