linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH 0/7] genirq/affinity: abstract new API from managed irq affinity spread
Date: Mon, 26 Jul 2021 18:37:31 +0800	[thread overview]
Message-ID: <YP6Qa8gWmbZg+HAN@T590> (raw)
In-Reply-To: <20210719095729.834332-1-ming.lei@redhat.com>

Hello Guys,

On Mon, Jul 19, 2021 at 05:57:22PM +0800, Ming Lei wrote:
> Hello,
> 
> irq_build_affinity_masks() actually grouping CPUs evenly into each managed
> irq vector according to NUMA and CPU locality, and it is reasonable to abstract
> one generic API for grouping CPUs evenly, the idea is suggested by Thomas
> Gleixner.
> 
> group_cpus_evenly() is abstracted and put into lib/, so blk-mq can re-use
> it to build default queue mapping.
> 
> Please comments!

Any comments on this patchset?


Thanks,
Ming


      parent reply	other threads:[~2021-07-26 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  9:57 [RFC PATCH 0/7] genirq/affinity: abstract new API from managed irq affinity spread Ming Lei
2021-07-19  9:57 ` [RFC PATCH 1/7] genirq/affinity: remove the 'firstvec' parameter from irq_build_affinity_masks Ming Lei
2021-07-19  9:57 ` [RFC PATCH 2/7] genirq/affinity: pass affinity managed mask array to irq_build_affinity_masks Ming Lei
2021-07-19  9:57 ` [RFC PATCH 3/7] genirq/affinity: don't pass irq_affinity_desc " Ming Lei
2021-07-19  9:57 ` [RFC PATCH 4/7] genirq/affinity: rename irq_build_affinity_masks as group_cpus_evenly Ming Lei
2021-07-19  9:57 ` [RFC PATCH 5/7] genirq/affinity: move group_cpus_evenly() into lib/ Ming Lei
2021-07-19  9:57 ` [RFC PATCH 6/7] lib/group_cpus: allow to group cpus in case of !CONFIG_SMP Ming Lei
2021-07-19  9:57 ` [RFC PATCH 7/7] blk-mq: build default queue map via group_cpus_evenly() Ming Lei
2021-07-26 10:37 ` Ming Lei [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=YP6Qa8gWmbZg+HAN@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).