From: Ming Lei <ming.lei@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org,
Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCH V6 0/2] genriq/affinity: Make vectors allocation fair
Date: Sun, 25 Aug 2019 16:02:13 +0800 [thread overview]
Message-ID: <20190825080212.GA17265@ming.t460p> (raw)
In-Reply-To: <20190819124937.9948-1-ming.lei@redhat.com>
On Mon, Aug 19, 2019 at 08:49:35PM +0800, Ming Lei wrote:
> Hi Thomas,
>
> The 1st patch makes __irq_build_affinity_masks() more reliable, such as,
> all nodes can be covered in the spread.
>
> The 2nd patch spread vectors on node according to the ratio of this node's
> CPU number to number of all remaining CPUs, then vectors assignment can
> become more fair. Meantime, the warning report from Jon Derrick can be
> fixed.
>
> Please consider it for V5.4.
>
> V6:
> - fix build waring reported by zero day, and extra change is only
> done on irq_build_affinity_masks()
>
> V5:
> - remove patch 1 of V4, which is wrong
> - handle vector wrapping because the 'start vector' may begin
> anywhere, especially for the 2nd stage spread
> - add more comment on the vector allocation algorithm
> - cleanup code a bit
> - run more tests to verify the change, which always get the
> expected result. Covers lots of num_queues, numa topo, CPU
> unpresent setting.
>
> V4:
> - provide proof why number of allocated vectors for each node is <= CPU
> count of this node
>
> V3:
> - re-order the patchset
> - add helper of irq_spread_vectors_on_node()
> - handle vector spread correctly in case that numvecs is > ncpus
> - return -ENOMEM to API's caller
>
> V2:
> - add patch3
> - start to allocate vectors from node with minimized CPU number,
> then every node is guaranteed to be allocated at least one vector.
> - avoid cross node spread
>
>
>
> Ming Lei (2):
> genirq/affinity: Improve __irq_build_affinity_masks()
> genirq/affinity: Spread vectors on node according to nr_cpu ratio
>
> kernel/irq/affinity.c | 231 ++++++++++++++++++++++++++++++++++++------
> 1 file changed, 201 insertions(+), 30 deletions(-)
>
> Cc: Jens Axboe <axboe@kernel.dk>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Keith Busch <kbusch@kernel.org>
> Cc: linux-nvme@lists.infradead.org,
> Cc: Jon Derrick <jonathan.derrick@intel.com>
> --
> 2.20.1
>
Hi Thomas,
Gentle ping on the two patches.
Thanks,
Ming
next prev parent reply other threads:[~2019-08-25 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:49 [PATCH V6 0/2] genriq/affinity: Make vectors allocation fair Ming Lei
2019-08-19 12:49 ` [PATCH V6 1/2] genirq/affinity: Improve __irq_build_affinity_masks() Ming Lei
2019-08-22 16:03 ` Keith Busch
2019-08-22 16:36 ` Derrick, Jonathan
2019-08-19 12:49 ` [PATCH V6 2/2] genirq/affinity: Spread vectors on node according to nr_cpu ratio Ming Lei
2019-08-19 13:13 ` Thomas Gleixner
2019-08-19 13:52 ` Ming Lei
2019-08-19 14:02 ` Thomas Gleixner
2019-08-22 3:09 ` Ming Lei
2019-08-22 16:03 ` Keith Busch
2019-08-22 16:36 ` Derrick, Jonathan
2019-08-25 8:02 ` Ming Lei [this message]
2019-08-25 9:45 ` [PATCH V6 0/2] genriq/affinity: Make vectors allocation fair Thomas Gleixner
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=20190825080212.GA17265@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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