LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ming Lei <ming.lei@canonical.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	Jens Axboe <axboe@kernel.dk>, Zach Brown <zab@zabbo.net>,
	Maxim Patlasov <mpatlasov@parallels.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: [PATCH v2 0/4] block & aio: improve loop with kernel aio
Date: Wed, 14 Jan 2015 18:17:24 +0800	[thread overview]
Message-ID: <CACVXFVOioFRNbDBJtBaG6za3gq01FdThQsocS42Ecd5UR5X0pg@mail.gmail.com> (raw)
In-Reply-To: <20150113162307.GA21338@infradead.org>

On Wed, Jan 14, 2015 at 12:23 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Jan 13, 2015 at 11:44:44PM +0800, Ming Lei wrote:
>> Follows benefits from using kernel aio in loop:
>>       - avoid double cache, and memory usage decreased a lot
>>       - system load gets much decreased
>
> This seems to conflate two changes:
>
>  1) use direct I/O
>  2) use aio (require 1)
>
> what numbers do you get when just using direct I/O?

I don't run the direct I/O only test because it needs quite
changes on current patches, such as: make the kiocb
as sync, allow all dio requests running concurrently for
sake of throughput.

IMO, without aio, context switches will be increased
inevitably, and CPU will be wasted, so could you explain
if there is advantage of not using aio?

Thanks,
Ming Lei

      reply	other threads:[~2015-01-14 10:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 15:44 [PATCH v2 0/4] block & aio: improve loop with kernel aio Ming Lei
2015-01-13 15:44 ` [PATCH v2 1/4] aio: add aio_kernel_() interface Ming Lei
2015-01-25 13:31   ` Christoph Hellwig
2015-01-26 16:18     ` Ming Lei
2015-01-26 17:00       ` Christoph Hellwig
2015-01-27 13:57         ` Ming Lei
2015-01-27 17:59       ` Christoph Hellwig
2015-01-13 15:44 ` [PATCH v2 2/4] fd/direct-io: introduce should_dirty for kernel aio Ming Lei
2015-01-25 13:34   ` Christoph Hellwig
2015-01-27 16:05     ` Ming Lei
2015-01-13 15:44 ` [PATCH v2 3/4] block: loop: introduce 'use_aio' sysfs file Ming Lei
2015-01-25 13:35   ` Christoph Hellwig
2015-01-27  5:26     ` Ming Lei
2015-01-26 17:57   ` Jeff Moyer
2015-01-13 15:44 ` [PATCH v2 4/4] block: loop: support to submit I/O via kernel aio based Ming Lei
2015-01-25 13:40   ` Christoph Hellwig
2015-03-18 18:28   ` Maxim Patlasov
2015-03-19  2:57     ` Ming Lei
2015-03-19 16:37       ` Maxim Patlasov
2015-03-20  5:27         ` Ming Lei
2015-01-13 16:23 ` [PATCH v2 0/4] block & aio: improve loop with kernel aio Christoph Hellwig
2015-01-14 10:17   ` Ming Lei [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=CACVXFVOioFRNbDBJtBaG6za3gq01FdThQsocS42Ecd5UR5X0pg@mail.gmail.com \
    --to=ming.lei@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=bcrl@kvack.org \
    --cc=dave.kleikamp@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatlasov@parallels.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zab@zabbo.net \
    /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;
as well as URLs for NNTP newsgroup(s).