From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: IPoIB multiqueue support?
Date: Tue, 11 May 2010 14:58:08 -0600 [thread overview]
Message-ID: <20100511205808.GS15969@obsidianresearch.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005111548450.8388-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
On Tue, May 11, 2010 at 03:50:35PM -0500, Christoph Lameter wrote:
> > To go multi-queue you'd create multiple QPs and spread the MGID binds
> > amongst them.
>
> It would be best to bind them to the QP of the local processor (assuming
> that the process continues to run on that processor).
Yes
> What about unicast traffic? One QP gets all unicast?
IIRC, there are some HCA-specific features for spreading traffic
amongst QPs using a hash of the IP/TCP/UDP headers. I don't know
anything about them though.
Within the standard IB functionality the best you could do is to
create a wack of QPs and then return different QPNs in your ARP
replies. Though this is very limited and probably not worth doing.
> > Yes, but the downside is that if you rely on the kernel to the group
> > join then the HCA will send the packet to user space and the kernel QP.
> >
> > Some of the weird features in the RDMA CM seem to be for supporting
> > this..
>
> The UMCAST flag can stop the kernel from processing the IGMP reply.
I'm not talking about IGMP, but the IB version of IGMP, the kernel
joins the group in IB land and also attaches the IPOIB QP. This can
all be faked out in userspace, but it isn't entirely straightforward.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-11 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 21:08 IPoIB multiqueue support? Christoph Lameter
[not found] ` <alpine.DEB.2.00.1005101607580.17916-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-05-10 21:12 ` Roland Dreier
[not found] ` <adawrvbxxyd.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-11 13:53 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1005110851530.1500-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-05-11 15:56 ` Roland Dreier
[not found] ` <adawrvawhyc.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-11 20:17 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1005111516500.1500-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-05-11 20:43 ` Jason Gunthorpe
[not found] ` <20100511204358.GQ15969-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-05-11 20:50 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1005111548450.8388-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-05-11 20:58 ` Jason Gunthorpe [this message]
[not found] ` <20100511205808.GS15969-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-05-11 22:11 ` Christoph Lameter
2010-05-11 21:52 ` Roland Dreier
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=20100511205808.GS15969@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
/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