From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@fb.com>
Cc: linux-block@vger.kernel.org, ming.lei@redhat.com, hch@lst.de
Subject: Re: [PATCH v2 0/6] Fixup mtip32xx for scheduling
Date: Fri, 28 Apr 2017 16:10:22 +0200 [thread overview]
Message-ID: <20170428141022.GB32073@lst.de> (raw)
In-Reply-To: <1493388117-15185-1-git-send-email-axboe@fb.com>
On Fri, Apr 28, 2017 at 08:01:49AM -0600, Jens Axboe wrote:
> Round two of this patchset to cleanup. Changes since the first
> posting:
I got two mixed series in my inbox, one with two patches and one with
6. The two patch one doesn't seem to have a cover letter.
>
> - Mark internal commands as REQ_OP_DRV_IN. Doesn't really matter
> what the data direction is, the important bit is that we need
> to ensure the request is seen as a passthrough.
Yes, I think that's the right thing to do. I'll review the details.
> - Utilize blk-mq timeout infrastructure, to avoid racing with
> cleanup.
Nice.
next prev parent reply other threads:[~2017-04-28 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 14:01 [PATCH v2 0/6] Fixup mtip32xx for scheduling Jens Axboe
2017-04-28 14:01 ` [PATCH 1/2] mtip32xx: convert internal command issue to block IO path Jens Axboe
2017-04-28 14:01 ` [PATCH 1/6] mtip32xx: get rid of 'atomic' argument to mtip_exec_internal_command() Jens Axboe
2017-04-28 14:01 ` [PATCH 2/2] Revert "mtip32xx: pass BLK_MQ_F_NO_SCHED" Jens Axboe
2017-04-28 14:01 ` [PATCH 2/6] mtip32xx: kill atomic argument to mtip_quiesce_io() Jens Axboe
2017-04-28 14:01 ` [PATCH 3/6] mtip32xx: abstract out "are any commands active" helper Jens Axboe
2017-04-28 14:01 ` [PATCH 4/6] blk-mq: don't bypass scheduler for reserved requests Jens Axboe
2017-04-28 14:01 ` [PATCH 5/6] mtip32xx: convert internal command issue to block IO path Jens Axboe
2017-04-28 14:01 ` [PATCH 6/6] Revert "mtip32xx: pass BLK_MQ_F_NO_SCHED" Jens Axboe
2017-04-28 14:10 ` Christoph Hellwig [this message]
2017-04-28 14:13 ` [PATCH v2 0/6] Fixup mtip32xx for scheduling Jens Axboe
2017-04-28 14:14 ` Christoph Hellwig
2017-04-28 14:17 ` 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=20170428141022.GB32073@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox