All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Justin M. Forbes" <jforbes@fedoraproject.org>,
	Jeff Moyer <jmoyer@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	"v4.0" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] block: loop: avoiding too many pending per work I/O
Date: Wed, 6 May 2015 00:36:40 -0700	[thread overview]
Message-ID: <20150506073640.GA19532@infradead.org> (raw)
In-Reply-To: <CACVXFVNZRbgogP1M1G3GDdQTgQ5WUN+Tt4k4=5b2iJse3ADA4g@mail.gmail.com>

On Wed, May 06, 2015 at 01:17:33PM +0800, Ming Lei wrote:
> But I still prefer to dio/aio approach because double cache can
> be avoided, which is a big win in my previous tests.

Can yo respin and resend the patches?  With Al's iov_iter work and my
kiocb changes it should be fairly easy and non-intrusive to do.

  reply	other threads:[~2015-05-06  7:36 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 [this message]
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 ` [PATCH 0/2] block: loop: fix stacked loop and performance regression Justin M. Forbes

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=20150506073640.GA19532@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=jforbes@fedoraproject.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=stable@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.