From: Christoph Hellwig <hch@infradead.org>
To: Shaohua Li <shli@fb.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ide@vger.kernel.org, Kernel-team@fb.com,
Jens Axboe <axboe@fb.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/2] block: support different tag allocation policy
Date: Mon, 15 Dec 2014 08:57:12 -0800 [thread overview]
Message-ID: <20141215165712.GA27010@infradead.org> (raw)
In-Reply-To: <20141215162443.GA3147371@devbig257.prn2.facebook.com>
On Mon, Dec 15, 2014 at 08:24:43AM -0800, Shaohua Li wrote:
> The policy for blkmq will be added later.
It doesn't make sense to move libata to block layer tagging before this
has been sorted out.
prev parent reply other threads:[~2014-12-15 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 3:21 [PATCH 1/2] block: support different tag allocation policy Shaohua Li
2014-12-15 3:21 ` [PATCH 2/2] libata: use generic taging Shaohua Li
2014-12-15 8:13 ` Christoph Hellwig
2014-12-15 8:08 ` [PATCH 1/2] block: support different tag allocation policy Christoph Hellwig
2014-12-15 16:24 ` Shaohua Li
2014-12-15 16:57 ` Christoph Hellwig [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=20141215165712.GA27010@infradead.org \
--to=hch@infradead.org \
--cc=Kernel-team@fb.com \
--cc=axboe@fb.com \
--cc=linux-ide@vger.kernel.org \
--cc=shli@fb.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).