All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, linux-cifs@vger.kernel.org,
	linux-nfs@vger.kernel.org, v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3] rdma: Enable ib_alloc_cq to spread work over a device's comp_vectors
Date: Mon, 05 Aug 2019 12:02:36 -0400	[thread overview]
Message-ID: <1d2aadf8054b3ba2c50464e17fc477eb92bcf1b1.camel@redhat.com> (raw)
In-Reply-To: <20190729171923.13428.52555.stgit@manet.1015granger.net>

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

On Mon, 2019-07-29 at 13:22 -0400, Chuck Lever wrote:
> Send and Receive completion is handled on a single CPU selected at
> the time each Completion Queue is allocated. Typically this is when
> an initiator instantiates an RDMA transport, or when a target
> accepts an RDMA connection.
> 
> Some ULPs cannot open a connection per CPU to spread completion
> workload across available CPUs and MSI vectors. For such ULPs,
> provide an API that allows the RDMA core to select a completion
> vector based on the device's complement of available comp_vecs.
> 
> ULPs that invoke ib_alloc_cq() with only comp_vector 0 are converted
> to use the new API so that their completion workloads interfere less
> with each other.
> 
> Suggested-by: Håkon Bugge <haakon.bugge@oracle.com>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
> Cc: <linux-cifs@vger.kernel.org>
> Cc: <v9fs-developer@lists.sourceforge.net>

This looks reasonable to me Chuck, and we have plenty of time to test it
in for-next before the next merge window, so applied to for-next, thanks
:-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-08-05 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 17:22 [PATCH v3] rdma: Enable ib_alloc_cq to spread work over a device's comp_vectors Chuck Lever
2019-08-05 16:02 ` Doug Ledford [this message]
2019-08-05 16:09 ` Bart Van Assche
2019-08-05 17:15   ` Chuck Lever

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=1d2aadf8054b3ba2c50464e17fc477eb92bcf1b1.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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.