On Tue, Dec 1, 2009 at 9:58 AM, Sasha Khapyorsky <[email protected]> wrote: > On 14:48 Mon 30 Nov , Hal Rosenstock wrote: >> >> The multicast tree (MLID) has one rate, MTU, etc. so these parameters >> should be enforced on multicast groups (MGIDs) overlaid on the same >> MLID. > > Assuming that Multicast groups (MGIDs) are consistent in terms of rate, > MTU and packet life time parameters. Why should we share this over MLID > implementing MGID to MLID compression? > > Sharing P_Key helps to prevent P_Key violation traps,
Actually, that's a simplification not strictly required. One example where that is the case is if there is no PKey enforcement in the subnet. > but what should be a reason for rate, MTU and packet life time? As with any path (which in this case is the multicast tree), there is a rate, MTU, and packet life time. As one example, if the tree does not support the MTU, then MTU discards can occur. There are other more subtle things that occur based on rate mismatches (overagressive transmitters). These should be precluded rather than allowed (and then having to debug the resulting issues). -- Hal > > Sasha > -- 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
