From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] blk-mq: code clean-up by adding an API to clear set->mq_map
Date: Mon, 02 Jul 2018 22:20:03 +0900 [thread overview]
Message-ID: <1530537603.13674.8.camel@gmail.com> (raw)
In-Reply-To: <20180702130227.gjpblurxccjqechl@linux-x5ow.site>
Hi Johannes,
I appreciate your kindly response.
On Mon, 2018-07-02 at 15:02 +0200, Johannes Thumshirn wrote:
> On Mon, Jul 02, 2018 at 09:55:57PM +0900, Minwoo Im wrote:
> >
> > No 2nd follow-up patch will be there. I thought these two parts are
> > using a same unit-function to clear the set->mq-map. Also thought it
> > would be great for the future use when it needs to be cleared.
> > However, as you mentioned, I totally agree with your point. It seems
> > just churns for churns' sake with no more usage for now.
> I actually mis-read your patch, I'm sorry.
>
> You're consolidating two callers of this so I guess this is not so
> problematic. I somehow ignored the first hunk in the patch.
>
> You could still evaluate if it isn't worth to make it:
> +static void blk_mq_clear_mq_map(struct blk_mq_tag_set *set)
> +{
> + int cpu;
> +
> + for_each_possible_cpu(cpu)
> + set->mq_map[cpu] = 0;
> +}
>
> and put it into 'include/linux/blk-mq.h'.
Do you mean this whole bunch of function should be moved into blk-mq.h with
'inline' format?
I have already added this function prototype to blk-mq.h without 'static' to
make blk-mq-pci.c to use it.
If you don't mind, can you please elaborate a little bit more?
Thanks,
Minwoo Im
>
> Johannes
next prev parent reply other threads:[~2018-07-02 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 16:21 [PATCH] blk-mq: code clean-up by adding an API to clear set->mq_map Minwoo Im
2018-07-02 8:15 ` Johannes Thumshirn
2018-07-02 12:55 ` Minwoo Im
2018-07-02 13:02 ` Johannes Thumshirn
2018-07-02 13:20 ` Minwoo Im [this message]
2018-07-02 13:27 ` Johannes Thumshirn
2018-07-02 13:34 ` Minwoo Im
2018-07-02 13:41 ` Johannes Thumshirn
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=1530537603.13674.8.camel@gmail.com \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@kernel.dk \
--cc=jthumshirn@suse.de \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).