From: Alexander Gordeev <agordeev@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>
Subject: Re: scsi-mq updated to latest linux-block/new-queue
Date: Wed, 9 Oct 2013 21:46:58 +0200 [thread overview]
Message-ID: <20131009194658.GA3066@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <1381345971.19256.461.camel@haakon3.risingtidesystems.com>
On Wed, Oct 09, 2013 at 12:12:51PM -0700, Nicholas A. Bellinger wrote:
> Just a heads up that the scsi-mq alpha branch has been updated to Jen's
> latest linux-block/new-queue containing hch's recent blk-mq
> improvements, along with Alexander's patch for the is_flush_fua +
> queue_depth=1 bug.
Oh, I have not expected it could be picked up. In fact I agree it needs
to be updated with what you spotted:
"Also, these extra increments should probably happen only when the passed
queue_depth == 1 && reserved_tags == 0."
What is the criteria for patches to include in your tree? I would suggest
to consider this one https://lkml.org/lkml/2013/8/9/90 if it fits.
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2013-10-09 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 19:12 Nicholas A. Bellinger
2013-10-09 19:46 ` Alexander Gordeev [this message]
2013-10-09 20:13 ` Nicholas A. Bellinger
2013-10-10 19:17 ` Christoph Hellwig
2013-10-10 19:32 ` Alexander Gordeev
2013-10-11 12:19 ` Christoph Hellwig
2013-10-11 14:23 ` Jens Axboe
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=20131009194658.GA3066@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.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
all inboxes | Powered by JetHome®