From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <keith.busch@intel.com>, Mike Snitzer <snitzer@redhat.com>
Cc: jmoyer@redhat.com, shivakrishna.merla@netapp.com,
dm-devel@redhat.com, Bart Van Assche <bvanassche@acm.org>
Subject: Re: awful request merge results while simulating high IOPS multipath
Date: Wed, 25 Feb 2015 07:11:41 -0800 [thread overview]
Message-ID: <54EDE62D.7010308@kernel.dk> (raw)
In-Reply-To: <alpine.LNX.2.00.1502250401330.32385@localhost.lm.intel.com>
On 02/24/2015 08:14 PM, Keith Busch wrote:
> To be honest, we also see underwhelming performance on high IOPS PCIe
> SSDs. We know of some bottlenecks and ideas to test, but hoping to work
> out the kinks in those ideas before Vault in two weeks.
Related to merging, or?
--
Jens Axboe
next prev parent reply other threads:[~2015-02-25 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 16:44 [PATCH 0/4] dm: simplify request-based DM a bit and an RFC-like perf tweak Mike Snitzer
2015-02-24 16:44 ` [PATCH 1/4] dm: remove unnecessary wrapper around blk_lld_busy Mike Snitzer
2015-02-24 16:44 ` [PATCH 2/4] dm: remove request-based DM queue's lld_busy_fn hook Mike Snitzer
2015-02-24 16:44 ` [PATCH 3/4] dm: remove request-based logic from make_request_fn wrapper Mike Snitzer
2015-02-24 16:44 ` [RFC PATCH 4/4] dm: delay running the queue slightly during request completion Mike Snitzer
2015-02-24 16:51 ` Jens Axboe
2015-02-24 17:22 ` [RFC PATCH 4/4 v2] " Mike Snitzer
2015-02-24 17:52 ` Jens Axboe
2015-02-24 18:12 ` Mike Snitzer
2015-02-24 18:16 ` Jens Axboe
2015-02-24 18:32 ` Mike Snitzer
2015-02-25 0:56 ` awful request merge results while simulating high IOPS multipath Mike Snitzer
2015-02-25 4:14 ` Keith Busch
2015-02-25 15:11 ` Jens Axboe [this message]
2015-02-25 18:17 ` Busch, Keith
2015-02-25 22:10 ` Mike Snitzer
2015-02-25 23:57 ` Keith Busch
2015-02-26 0:11 ` Mike Snitzer
2015-02-26 0:28 ` Keith Busch
2015-02-25 4:38 ` FIXED! [was: awful request merge results while simulating high IOPS] multipath Mike Snitzer
2015-02-25 4:41 ` Mike Snitzer
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=54EDE62D.7010308@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=jmoyer@redhat.com \
--cc=keith.busch@intel.com \
--cc=shivakrishna.merla@netapp.com \
--cc=snitzer@redhat.com \
/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.