From: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Alex Vesker <valex-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/2] rdma-core: Provide missing user space pieces for multicast sendonly join V2
Date: Tue, 14 Nov 2017 12:57:20 -0600 [thread overview]
Message-ID: <20171114185720.609975150@linux.com> (raw)
V1->V2
- Fix comments and API spec
- Improve test code.
The userspace portion that enables to join a multicast group only for sending
was not merged when the kernel portion was merged.
The patches are straightforward and have been used by us for quite some time.
We were surprised when the new distro releases where missing these definitions
and we had to add these patches manually again.
This adds what is missing.
--
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 reply other threads:[~2017-11-14 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 18:57 Christoph Lameter [this message]
2017-11-14 18:57 ` [PATCH 1/2] librdmacm: Add support for extended join multicast API V2 Christoph Lameter
[not found] ` <20171114185739.838757957-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2017-11-14 19:25 ` Jason Gunthorpe
[not found] ` <20171114192558.GL4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 19:50 ` Christopher Lameter
2017-11-14 19:56 ` Jason Gunthorpe
[not found] ` <20171114195659.GP4263-uk2M96/98Pc@public.gmane.org>
2017-11-15 15:22 ` Christopher Lameter
2017-11-17 22:22 ` Jason Gunthorpe
2017-11-20 19:46 ` Jason Gunthorpe
2017-11-14 18:57 ` [PATCH 2/2] librdmacm: Mckey test support for send only full member Christoph Lameter
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=20171114185720.609975150@linux.com \
--to=cl-vytec60ixjuavxtiumwx3w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=valex-VPRAkNaXOzVWk0Htik3J/w@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