From: Christoph Hellwig <hch@infradead.org>
To: Shaohua Li <shli@fb.com>
Cc: 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 00:08:13 -0800 [thread overview]
Message-ID: <20141215080813.GA3982@infradead.org> (raw)
In-Reply-To: <e0ea802ef0d4170ad409e5dbf814c28581c091ac.1418613253.git.shli@fb.com>
On Sun, Dec 14, 2014 at 07:21:49PM -0800, Shaohua Li wrote:
> The libata tag allocation is using a round-robin policy. Next patch will
> make libata use block generic tag allocation, so let's add a policy to
> tag allocation.
>
> Currently two policies: FIFO (default) and round-robin.
What's the benefit of round robin allocation? Why do you only need
it for the old simple allocator, and no policy control for the more
complex blkpmq allocator?
next prev parent reply other threads:[~2014-12-15 8:08 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 ` Christoph Hellwig [this message]
2014-12-15 16:24 ` [PATCH 1/2] block: support different tag allocation policy Shaohua Li
2014-12-15 16:57 ` Christoph Hellwig
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=20141215080813.GA3982@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).