From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.com>, <g@nvidia.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
<bart.vanassche@wdc.com>
Subject: Re: [PATCH] RDMA/srp: Fix support for unpopulated and unbalanced NUMA nodes
Date: Fri, 12 Feb 2021 13:21:22 -0400 [thread overview]
Message-ID: <20210212172122.GA1722574@nvidia.com> (raw)
In-Reply-To: <9cb4d9d3-30ad-2276-7eff-e85f7ddfb411@suse.com>
On Fri, Feb 05, 2021 at 09:14:28AM +0100, Nicolas Morey-Chaisemartin wrote:
> The current code computes a number of channels per SRP target and spreads
> them equally across all online NUMA nodes.
> Each channel is then assigned a CPU within this node.
>
> In the case of unbalanced, or even unpopulated nodes, some channels
> do not get a CPU associated and thus do not get connected.
> This causes the SRP connection to fail.
>
> This patch solves the issue by rewriting channel computation and allocation:
> - Drop channel to node/CPU association as it had
> no real effect on locality but added unnecessary complexity.
> - Tweak the number of channels allocated to reduce CPU contention when possible:
> - Up to one channel per CPU (instead of up to 4 by node)
> - At least 4 channels per node, unless ch_count module parameter is used.
>
> Signed-off-by: Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.com>
> ---
> drivers/infiniband/ulp/srp/ib_srp.c | 110 ++++++++++++----------------
> 1 file changed, 45 insertions(+), 65 deletions(-)
Bart?
Jason
next prev parent reply other threads:[~2021-02-12 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 8:14 [PATCH] RDMA/srp: Fix support for unpopulated and unbalanced NUMA nodes Nicolas Morey-Chaisemartin
2021-02-12 17:21 ` Jason Gunthorpe [this message]
2021-02-12 19:30 ` Bart Van Assche
2021-02-17 13:37 ` Jason Gunthorpe
2021-03-15 3:30 ` Yi Zhang
2021-03-15 7:56 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2021-03-17 7:45 Yi Zhang
2021-03-19 9:49 ` Greg KH
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=20210212172122.GA1722574@nvidia.com \
--to=jgg@nvidia.com \
--cc=bart.vanassche@wdc.com \
--cc=g@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=nmoreychaisemartin@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.