From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34032A0540; Mon, 3 Aug 2020 19:19:42 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C3CE21C020; Mon, 3 Aug 2020 19:19:41 +0200 (CEST) Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) by dpdk.org (Postfix) with ESMTP id 9638F2BD8 for ; Mon, 3 Aug 2020 19:19:39 +0200 (CEST) Received: by mail-ej1-f43.google.com with SMTP id bo3so16825258ejb.11 for ; Mon, 03 Aug 2020 10:19:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DseFISb6nOBnw4kaa9H7mSSbmrYbwaVI0UdLye2NYbA=; b=e7769Zn4gSSeOmfKHNqvKm8aVrQ23tGMSK396pzwsrvLRMjbk8zxIwz9R2sBz+iW42 13Vh6MHRtrtjm2CUuen64McwNBsF65VK/iKI4D4cayvxpxgEJQTI3aplLxjFI5lsqiOz 2EdMA7zskVS2YBt21lAqxfSF/svcP4nRcHKj0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DseFISb6nOBnw4kaa9H7mSSbmrYbwaVI0UdLye2NYbA=; b=OUNHYZCh2ANOM4l8WWrBzK+BDnJKAFyuzdVTRyZ5rfdPS51M2yFiikF9OpHZtuX4nC 37NCNoGyJxTlZ5tzjuV64UX7M+/Kv9MZSvI/g8jCn7KcNES/ueJrhdUNJLDEXGr0l63C 5pOSap7FYXkhAOjplf/wbGZfxKRIc8pgZUSz8isHptwcmPRhquMcBUqmbCkDplnYT4ep k3jZrL6dcCHKXAKwChiLP8IfCSPgQOwB+odbW39qhXwl3BQvJ5ShQVkm4Zm8ZmEuTX1p e/GVvoaO4ScnbHGB5ub4M7tATnvb32QrG+7K7P47mVbhohaV0p8GSa3etW7DLYMBJ8Hp 9EDw== X-Gm-Message-State: AOAM5336XcWTXj7M987nDGW1NXFTHRAy9a9iGJhQlS98wQ4b+9g1bpGH V0Xv4ZoUm+ber7toxkj60eyuxK8XDrKc8gHGBOISV5GRAGw0 X-Google-Smtp-Source: ABdhPJzESR0JwHYEX3s/z/5pslPSPOWFs101pHDzKzgbNobLrsWI8uPR+izHFcysAY1hTZWdHls9bIsvKC5EBmpEQoA= X-Received: by 2002:a17:906:7e4e:: with SMTP id z14mr17231716ejr.87.1596475179132; Mon, 03 Aug 2020 10:19:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Daniel Kirichok Date: Mon, 3 Aug 2020 13:19:28 -0400 Message-ID: To: dts@dpdk.org Cc: Lincoln Lavoie , dev@dpdk.org, David Liu , Owen Hilyard Content-Type: multipart/alternative; boundary="000000000000f2026105abfc57f0" Subject: Re: [dts] Idem with Multicast Packets Feature X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" --000000000000f2026105abfc57f0 Content-Type: text/plain; charset="UTF-8" Hi all, I wanted to send a follow up question regarding the development of the Idem for Multicast Packets feature. Based on the plan we have so far, it involves having one port be designated to send the packet, and two ports be designated to receive the packet. In order to send out one packet for the two ports to receive, it looks like this would require for all three ports to be on the same network and a 1-2 pairing configuration would be needed on the server. Is this the right approach for developing this feature? Would an alternate approach be better to avoid server reconfiguration such as sending out a multicast packet from each of the ports (two total packets sent out) and see if they each receive what was sent? Thanks, Dan On Fri, Jul 10, 2020 at 1:27 PM Daniel Kirichok wrote: > Hi all, > > The Idem with Multicast Packets test will first create three groups of > port combinations. The first group will have both ports be capable of > receiving a packet. The second group will have one port be open to receive > a packet and one be closed. The third group will have both ports be closed. > Each of the ports will be pinged to ensure that they are reachable. > Afterwards, a packet will be generated and sent to each of these groups, > and it will ensure that the correct behavior of a failed or successful > delivery occurs on each port. > > Let me know if there are any comments or questions. > > Thanks, > Dan > > -- > > Dan Kirichok > > UNH InterOperability Laboratory > > 21 Madbury Rd, Suite 100, Durham, NH 03824 > > dkirichok@iol.unh.edu > > www.iol.unh.edu > > > > -- Dan Kirichok UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 dkirichok@iol.unh.edu www.iol.unh.edu --000000000000f2026105abfc57f0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I wanted to send a follow up question regar= ding the development of the Idem for Multicast Packets feature. Based on th= e plan we have so far, it involves having one port be designated to send th= e packet, and two ports be designated to receive the packet. In order to se= nd out one packet for the two ports to receive, it looks like this would re= quire for all three ports to be on the same network and a 1-2 pairing confi= guration would be needed on the server. Is this the right approach for deve= loping this feature? Would an alternate approach be better to avoid server = reconfiguration such as sending out a multicast packet from each of the por= ts (two total packets sent out) and see if they each receive what was sent?=

Thanks,
Dan

On Fri, Jul 10, 2020 at = 1:27 PM Daniel Kirichok <dkiric= hok@iol.unh.edu> wrote:
Hi all,

The Idem with Mu= lticast Packets test will first create three groups of port combinations. T= he first group will have both ports be capable of receiving a packet. The s= econd group will have one port be open to receive a packet and one be close= d. The third group will have both ports be closed. Each of the ports will b= e pinged to ensure that they are reachable. Afterwards, a packet will be ge= nerated and sent=C2=A0to each of these groups, and it will ensure that the = correct behavior of a failed or successful delivery occurs on each port.=C2= =A0

Let me know if there are any comments or quest= ions.

Thanks,
Dan
=
--

Dan Kirichok

UNH InterOperabi= lity Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

dkirichok@iol.unh.edu

www.iol.unh.edu





--

Dan Kirichok

UNH InterOperability = Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

dkirichok@iol.unh.edu<= /p>

w= ww.iol.unh.edu



<= /div> --000000000000f2026105abfc57f0--