From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ipi_redirect vs rq_affinity
Date: Fri, 24 Jan 2014 11:11:29 -0800 [thread overview]
Message-ID: <20140124191129.GG7483@kernel.dk> (raw)
In-Reply-To: <20140124132234.GA8553@infradead.org>
On Fri, Jan 24 2014, Christoph Hellwig wrote:
> Hi Jens,
>
> it seems like blk-mq uses the ipi_redirect attribute in pretty much the
> same way as the old blk-softirq code used the rq_affinity one, except
> that the old code has an additional option to direct into any core in
> the current package.
>
> Is there any good reason to not reuse the old name and semantics?
It is pretty much the same. I don't like the semantics of the old one,
where it's 0/1/2 for off/on/different-on, though. Seems like now would
be a good time to clean it up.
--
Jens Axboe
next prev parent reply other threads:[~2014-01-24 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 13:22 ipi_redirect vs rq_affinity Christoph Hellwig
2014-01-24 19:11 ` Jens Axboe [this message]
2014-01-27 7:51 ` Christoph Hellwig
2014-01-27 19:16 ` 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=20140124191129.GG7483@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@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