David MacMhaon wrote:
>> I think multicast transmit is easy (just populate the ARP table
>> appropriately). I think multicast receive is also supported with recent
>> versions of the 10GbE yellow block. You could probably check the
>> mlib_devel git commit logs for the yellow block code to find
Marc is correct. The ARP table is not involved in multicast. The multicast
MAC is just mapped from the multicast IP.
Wesley New
South African SKA Project
+2721 506 7300
www.ska.ac.za
On Thu, Nov 5, 2015 at 12:51 PM, Marc Welz wrote:
> David MacMhaon wrote:
>
> >> I think
Thanks, All!
John
> Marc is correct. The ARP table is not involved in multicast. The multicast
> MAC is just mapped from the multicast IP.
>
> Wesley New
> South African SKA Project
> +2721 506 7300
> www.ska.ac.za
>
>
>
> On Thu, Nov 5, 2015 at 12:51 PM, Marc Welz wrote:
>
>>
As I think Jack commented, I was remembering an old trick that predated
multicast support in the core.
> On Nov 5, 2015, at 02:51, Marc Welz wrote:
>
> Not sure if the arp table is involved in this - the destination mac is
> (should be)
> generated algorithmically from the
Hi all.
Does the current ROACH-2 10 gbe yellow block work for multicast transmit?
Does anyone have an example of use of it, if so?
Thanks!
John
Hi John,
It works great! Transmit only is happily also the simplest use case.
If you're doing stuff from the powerPC which you want multicasting, I
believe you have to
invoke corr.katcp_wrapper.FpgaClient.tap_multicast_add_send(). If you only
want to multicast traffic from the FPGA (which is how
> Hi, John.
>
> I think multicast transmit is easy (just populate the ARP table
> appropriately). I think multicast receive is also supported with recent
> versions of the 10GbE yellow block. You could probably check the
> mlib_devel git commit logs for the yellow block code to find clues.
>
>
7 matches
Mail list logo