From: David Ahern <dsahern@kernel.org>
To: Zhu Yanjun <yanjun.zhu@linux.dev>,
Bob Pearson <rpearsonhpe@gmail.com>,
jgg@nvidia.com, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, rain.1986.08.12@gmail.com
Subject: Re: [PATCH for-next v6 3/7] RDMA/rxe: Register IP mcast address
Date: Fri, 8 Dec 2023 08:51:16 -0700 [thread overview]
Message-ID: <06f0cae8-03ab-474a-b8dd-40329339a4cc@kernel.org> (raw)
In-Reply-To: <488bcc6a-2198-4fbc-a12d-329a378d6ea2@linux.dev>
On 12/8/23 6:52 AM, Zhu Yanjun wrote:
> Hi, David Ahern
>
> About the functions ip_mc_join_group, ipv6_sock_mc_drop,
> ipv6_sock_mc_drop and ip_mc_leave_group,
>
> Can you share your advice about them?
see my previous comment on this patch.
next prev parent reply other threads:[~2023-12-08 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 19:29 [PATCH for-next v6 0/7] RDMA/rxe: Make multicast work Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 1/7] RDMA/rxe: Cleanup rxe_ah/av_chk_attr Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 2/7] RDMA/rxe: Fix sending of mcast packets Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 3/7] RDMA/rxe: Register IP mcast address Bob Pearson
2023-12-08 13:52 ` Zhu Yanjun
2023-12-08 15:51 ` David Ahern [this message]
2023-12-08 15:50 ` David Ahern
2023-12-09 11:32 ` Zhu Yanjun
2023-12-11 0:56 ` Bob Pearson
2023-12-11 2:01 ` David Ahern
2023-12-07 19:29 ` [PATCH for-next v6 4/7] RDMA/rxe: Let rxe_lookup_mcg use rcu_read_lock Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 5/7] RDMA/rxe: Split multicast lock Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 6/7] RDMA/rxe: Cleanup mcg lifetime Bob Pearson
2023-12-07 19:29 ` [PATCH for-next v6 7/7] RDMA/rxe: Add module parameters for mcast limits Bob Pearson
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=06f0cae8-03ab-474a-b8dd-40329339a4cc@kernel.org \
--to=dsahern@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rain.1986.08.12@gmail.com \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@linux.dev \
/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