From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <bvanassche@fusionio.com>,
Robert Elliott <Elliott@hp.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@ZenIV.linux.org.uk, Or Gerlitz <ogerlitz@mellanox.com>,
Oren Duer <oren@mellanox.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Mike Christie <michaelc@cs.wisc.edu>,
linux-fsdevel@vger.kernel.org, Max Gurtovoy <maxg@mellanox.com>
Subject: Re: Performance degradation in IO writes vs. reads (was scsi-mq V2)
Date: Thu, 21 Aug 2014 06:03:15 -0700 [thread overview]
Message-ID: <20140821130315.GB1567@infradead.org> (raw)
In-Reply-To: <53F5E6C9.1020207@dev.mellanox.co.il>
On Thu, Aug 21, 2014 at 03:32:09PM +0300, Sagi Grimberg wrote:
> So I just got back to checking this issue of *extremely low* IO write
> performance I got in 3.16-rc2.
Please test with 3.16 final. There once issue each in aio and dio
that caused bad I/O performance regression that were only fixed last
minute in the 3.16 cycle.
next prev parent reply other threads:[~2014-08-21 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1403715121-1201-1-git-send-email-hch@lst.de>
[not found] ` <20140708144829.GA5539@infradead.org>
[not found] ` <53C39F36.9010003@dev.mellanox.co.il>
2014-08-21 12:32 ` Performance degradation in IO writes vs. reads (was scsi-mq V2) Sagi Grimberg
2014-08-21 13:03 ` Christoph Hellwig [this message]
2014-08-21 14:02 ` Sagi Grimberg
2014-08-24 16:41 ` Sagi Grimberg
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=20140821130315.GB1567@infradead.org \
--to=hch@infradead.org \
--cc=Elliott@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@fusionio.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=oren@mellanox.com \
--cc=sagig@dev.mellanox.co.il \
--cc=viro@ZenIV.linux.org.uk \
/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).