> On 6/10/2015 3:10 PM, Jason Gunthorpe wrote: > > On Wed, Jun 10, 2015 at 01:47:36PM -0400, Hal Rosenstock wrote: > >> On 6/9/2015 10:57 AM, [email protected] wrote: > >>> From: Kaike Wan <[email protected]> > >>> > >>> This patch routes a SA pathrecord query to netlink first > >> > >> Should only unicast PRs be done in this manner or should API support > >> enabling for unicast and/or multicast ? > >> > >> AFAIK kernel doesn't query multicast PRs now (queries MCMRs) but this > >> seems like it would help make it future proof and not have to take > >> timeout on local query unless app supports it. > > > > It is a good question. We can clearly extend toward that, using a MGID > > as the DGID and adding additional nested netlink fields. > > > > However, does it make sense? > > If it doesn't make sense, then should MGIDs as DGIDs never be requested via > the PR netlink API ? >
Why should we prevent it? What does it hurt? Ira -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
