public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Yu Kuai <yukuai3@huawei.com>
Subject: Re: [PATCH 1/6] blk-mq: figure out correct numa node for hw queue
Date: Wed, 2 Mar 2022 17:22:10 +0800	[thread overview]
Message-ID: <Yh83Qma/MYWBNwiN@T590> (raw)
In-Reply-To: <7d112d9f-6ab1-4f8e-6005-b940074f1071@huawei.com>

On Wed, Mar 02, 2022 at 09:02:53AM +0000, John Garry wrote:
> On 02/03/2022 01:47, Ming Lei wrote:
> > > >    static struct blk_mq_tags *blk_mq_alloc_rq_map(struct blk_mq_tag_set *set,
> > > >    					       unsigned int hctx_idx,
> > > >    					       unsigned int nr_tags,
> > > >    					       unsigned int reserved_tags)
> > > >    {
> > > >    	struct blk_mq_tags *tags;
> > > > -	int node;
> > > > +	int node = blk_mq_get_hctx_node(set, hctx_idx);
> > > nit: the code originally had reverse firtree ordering, which I suppose is
> > > not by mistake
> > What is reverse firtree ordering here? I don't know what is wrong
> > with the above one line change from patch style viewpoint, and
> > checkpatch complains nothing here.
> 
> checkpath would not complain about this. I'm talking about:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-tip.rst#n587
> 
> The original code had:
> 
> 	struct blk_mq_tags *tags;
> 	int node;
> 
> as opposed to:
> 
> 	int node;
> 	struct blk_mq_tags *tags;
> 
> That's all. The block code seems to mostly follow this style when possible.
> It's just a style issue.

But my patch doesn't change the order, :-)


Thanks,
Ming


  reply	other threads:[~2022-03-02  9:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  9:04 [PATCH 0/6] blk-mq: update_nr_hw_queues related improvement & bugfix Ming Lei
2022-02-28  9:04 ` [PATCH 1/6] blk-mq: figure out correct numa node for hw queue Ming Lei
2022-03-01 13:30   ` Christoph Hellwig
2022-03-01 19:19   ` John Garry
2022-03-02  1:47     ` Ming Lei
2022-03-02  9:02       ` John Garry
2022-03-02  9:22         ` Ming Lei [this message]
2022-03-02 10:11           ` John Garry
2022-02-28  9:04 ` [PATCH 2/6] blk-mq: simplify reallocation of hw ctxs a bit Ming Lei
2022-03-01 13:30   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 3/6] blk-mq: re-config poll after queue map is changed Ming Lei
2022-03-01 13:31   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 4/6] block: mtip32xx: don't touch q->queue_hw_ctx Ming Lei
2022-03-01 13:32   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 5/6] blk-mq: add helper of blk_mq_get_hctx to retrieve hctx via its index Ming Lei
2022-03-01 13:33   ` Christoph Hellwig
2022-02-28  9:04 ` [PATCH 6/6] blk-mq: manage hctx map via xarray Ming Lei
2022-02-28 17:36   ` kernel test robot
2022-02-28 17:57   ` kernel test robot
2022-03-01  9:08     ` Ming Lei
2022-03-01 13:37   ` Christoph Hellwig
2022-03-02  2:06     ` Ming Lei
2022-03-02  8:24       ` Christoph Hellwig
2022-03-02  9:53         ` Ming Lei
2022-03-02  9:59           ` 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=Yh83Qma/MYWBNwiN@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=john.garry@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=yukuai3@huawei.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