From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) by dpdk.org (Postfix) with ESMTP id 50642DED for ; Tue, 28 Aug 2018 16:48:49 +0200 (CEST) Received: by mail-ed1-f52.google.com with SMTP id h4-v6so1587027edi.6 for ; Tue, 28 Aug 2018 07:48:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rVYUsXwktM2vsNfDoBcfPf+eJLMJwoI61IYO9whtaNw=; b=mMLDB2pLz8yeLv26Td9b8qTRowKhGpsWrbCZBzovyYrb4Hkupfgu2AvnkPP8PgWgbw 2x23Pyt91dQThTKfJmb2skBhW0baluclPwGuV9umWmheClXLNE8c6CqI9VBb6bKtg6BE VgTn2Of2zUO4/9FMMHhzm38ppCF7VxPevz7WTcbURuH812LVGk43LtUKYTgu1EPB6+Ri VdXzHRH/HxnUoLFI/JkUCF0zqwUbRg3ixuxlF23zhTnoYwvDuE5WnfhZSKT0jgjghjdQ 2KJ5sboBb7A3R3dFmTKsgB0xkhy65hK0e53x540q44Rmr+cqnJ61McVomZ/oWhssp16j /k+A== 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=rVYUsXwktM2vsNfDoBcfPf+eJLMJwoI61IYO9whtaNw=; b=mcz+cvzDUp6OgV+dV/sOYRmsWeIx5dUGoAFx5SkSQ+Ap//0rKu0pFsPVvdmHN58MR2 M3IH6dp/bjg/j68A+sfDZ5Yz/ugq3qbagcqwBv27xJZ0XM9WOZ54rnk80W/bINYrFQQN CFWm1Hvoy1Qj5evoncNqURnYmV5ENPjL1pYOu5f7R98zvOz6RBbZxGg2p11SKg4rbOcV te4ev0NWZM6/VMunomyZhnZ45CdRFRqQcsweGNrF602oxTTIkKlsMQ2iL63fOl0XXYMr VUkdcA25kP5OlQmjfYW5F5Wv1bpJwz+L1MCAFPUmRSOhOK8ugNbcwvTyag6KmYxFo5B6 tPKA== X-Gm-Message-State: APzg51AFBh899NHk2T7fVMkdHvmMMRgk2sDNcJ60teBJMm3iG4XXKWvS prNvxgBBdoGVuncENrWNqBDc0Eb8Bt3dlc0g6Ec= X-Google-Smtp-Source: ANB0VdbPIM7z14ADUDFrC8U2pQZy6lrqQW7ZJlrlR29i4mlvgMOHx3Ywpg8D5fwoWXnIXQ1hiM9TgNEM7w40yf4kJRc= X-Received: by 2002:a50:b4db:: with SMTP id x27-v6mr2786651edd.155.1535467728846; Tue, 28 Aug 2018 07:48:48 -0700 (PDT) MIME-Version: 1.0 References: <000801d43d36$ef9f7480$cede5d80$@ingenieurbuero-foss.de> <001401d43d76$fe69f860$fb3de920$@ingenieurbuero-foss.de> <001a01d43edc$147fbcf0$3d7f36d0$@ingenieurbuero-foss.de> <002b01d43edd$63438190$29ca84b0$@ingenieurbuero-foss.de> In-Reply-To: <002b01d43edd$63438190$29ca84b0$@ingenieurbuero-foss.de> From: Rami Rosen Date: Tue, 28 Aug 2018 17:48:37 +0300 Message-ID: To: Sebastian Foss Cc: dts@dpdk.org Content-Type: multipart/alternative; boundary="0000000000008ac25005747ff0a7" Subject: Re: [dts] DDP / testpmd setup 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: , X-List-Received-Date: Tue, 28 Aug 2018 14:48:49 -0000 --0000000000008ac25005747ff0a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Sebastian, How did you found out it goes all to queue 0 ? is it by running testpmd in RXonly mode, and setting it to verbose and looking in the content of the packets it shows on the console ? or by any other means ? Also can you describe your setup - is it with VMs, how do you send the traffic (scapy/pktgen/IXIA)? Regards, Rami Rosen On Tue, Aug 28, 2018 at 5:42 PM Sebastian Foss wrote: > I used the latest pppoe ddp from intel=E2=80=99s website and tried to map= /add > pctypes 15 and 17 to the hashing =E2=80=93 then run some pppoe when using= i40e > again and it still all goes to queue 0. > > > > testpmd> ddp get info /home/dpdktest/ppp-oe-ol2tpv2.pkgo > > Global Track id: 0x80000006 > > Global Version: 1.0.0.0 > > Global Package name: PPPoE and PPPoL2TPv2 > > > > i40e Profile Track id: 0x80000006 > > i40e Profile Version: 1.0.0.0 > > i40e Profile name: E710 PPPoE and PPPoL2TPv2 > > > > Package Notes: > > This profile enables PPPoE and PPPoL2TPv2 parsing > > L2TPv2 Tunnel ID extracted to field 46 > > L2TPv2/PPPoE Session ID extracted to field 47 > > PPP Protocol ID extracted to field 48 > > > > > > List of supported devices: > > 8086:1572 FFFF:FFFF > > 8086:1574 FFFF:FFFF > > 8086:1580 FFFF:FFFF > > 8086:1581 FFFF:FFFF > > 8086:1583 FFFF:FFFF > > 8086:1584 FFFF:FFFF > > 8086:1585 FFFF:FFFF > > 8086:1586 FFFF:FFFF > > 8086:1587 FFFF:FFFF > > 8086:1588 FFFF:FFFF > > 8086:1589 FFFF:FFFF > > 8086:158A FFFF:FFFF > > 8086:158B FFFF:FFFF > > > > List of used protocols: > > 12: IPV4 > > 13: IPV6 > > 15: GRENAT > > 17: TCP > > 18: UDP > > 19: SCTP > > 20: ICMP > > 22: L2TPv2CTRL > > 23: ICMPV6 > > 26: L2TPv2 > > 27: L2TPv2PAY > > 28: PPPoL2TPv2 > > 29: PPPoE > > 33: PAY2 > > 34: PAY3 > > 35: PAY4 > > 44: IPV4FRAG > > 48: IPV6FRAG > > 52: OIPV4 > > 53: OIPV6 > > > > List of defined packet classification types: > > 14: L2TPv2CTRL > > 15: PPPoE IPV4 > > 16: PPPoE IPV6 > > 17: PPPoE > > 18: PPPoL2TPv2 IPV4 > > 19: PPPoL2TPv2 IPV6 > > 20: PPPoL2TPv2 > > 21: L2TPv2PAY > > > > List of defined packet types: > > 154: PPPoE PAY2 > > 155: PPPoE IPV4FRAG PAY3 > > 156: PPPoE IPV4 PAY3 > > 157: PPPoE IPV4 UDP PAY4 > > 158: PPPoE IPV4 TCP PAY4 > > 159: PPPoE IPV4 SCTP PAY4 > > 160: PPPoE IPV4 ICMP PAY4 > > 161: PPPoE IPV6FRAG PAY3 > > 162: PPPoE IPV6 PAY3 > > 163: PPPoE IPV6 UDP PAY4 > > 164: PPPoE IPV6 TCP PAY4 > > 165: PPPoE IPV6 SCTP PAY4 > > 166: PPPoE IPV6 ICMPV6 PAY4 > > 167: OIPV4 L2TPv2 PPPoL2TPv2 PAY3 > > 168: OIPV4 L2TPv2 PPPoL2TPv2 IPV4FRAG PAY3 > > 169: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 PAY3 > > 170: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 UDP PAY4 > > 171: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 TCP PAY4 > > 172: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 SCTP PAY4 > > 173: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 ICMP PAY4 > > 174: OIPV4 L2TPv2 PPPoL2TPv2 IPV6FRAG PAY3 > > 175: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 PAY3 > > 176: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 UDP PAY4 > > 177: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 TCP PAY4 > > 178: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 SCTP PAY4 > > 179: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 ICMPV6 PAY4 > > 180: OIPV6 L2TPv2 PPPoL2TPv2 PAY3 > > 181: OIPV6 L2TPv2 PPPoL2TPv2 IPV4FRAG PAY3 > > 182: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 PAY3 > > 183: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 UDP PAY4 > > 184: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 TCP PAY4 > > 185: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 SCTP PAY4 > > 186: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 ICMP PAY4 > > 187: OIPV6 L2TPv2 PPPoL2TPv2 IPV6FRAG PAY3 > > 188: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 PAY3 > > 189: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 UDP PAY4 > > 190: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 TCP PAY4 > > 191: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 SCTP PAY4 > > 150: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 ICMPV6 PAY4 > > 12: OIPV4 L2TPv2 L2TPv2CTRL PAY4 > > 13: OIPV6 L2TPv2 L2TPv2CTRL PAY4 > > 14: OIPV4 L2TPv2 L2TPv2PAY PAY3 > > 15: OIPV6 L2TPv2 L2TPv2PAY PAY3 > > > > *Von:* Rami Rosen > *Gesendet:* Dienstag, 28. August 2018 16:38 > *An:* Sebastian Foss > *Cc:* dts@dpdk.org > *Betreff:* Re: [dts] DDP / testpmd setup > > > > Hi Sebastian, > > > > What do you get when running: > > > > testpmd> ddp get info (profile_path) > > > > See: > https://doc.dpdk.org/guides/testpmd_app_ug/testpmd_funcs.html > > > > Regards, > > Rami Rosen > > > > > > On Tue, Aug 28, 2018 at 5:33 PM Sebastian Foss > wrote: > > Hi, > > ok seems the ddp profiles are persistent when unbinding and rebinding the > dpdk / linux drivers. However it seems like the ddp profile is not used f= or > rss hashing when i bind the i40e driver and run some test (e.g. PPPoE > traffic). > > Are there any plans to support ddp profiles for rss hashing when i40e is > used without dpdk ? > > > > Thanks. > > > > *Von:* Rami Rosen > *Gesendet:* Sonntag, 26. August 2018 22:46 > *An:* Sebastian Foss > *Cc:* dts@dpdk.org > *Betreff:* Re: [dts] DDP / testpmd setup > > > > Hi, Sebastian, > > Regarding rebinding, there are two types: > > One is with > > dpdk-devbind -b i40e pci_id_of_port > > And the second is the ribust one: > > rmmod i40e and then modprobe i40e. I am not sure as to which of the two > you aim when talking about rebinding. > > I would suggest to start with the first option. It triggers calling the > probe() callback of I40E, and not the full longer and heavier way with I4= 0E > module_exit() and module_init() callbacks > > > > Regarding userspace app for achieving it: you can follow the dpdk testpmd > code, but > > this can take quite a time and effort. > > > > Regards, > > Rami Rosen > > > > > > =D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=9D =D7=90=D7=B3, 26 = =D7=91=D7=90=D7=95=D7=92=D7=B3 2018, 22:57, =D7=9E=D7=90=D7=AA Sebastian Fo= ss =E2=80=8F< > sfo@ingenieurbuero-foss.de>: > > Hi Rami, > > I found the switch for testpmd to use a cmd line script instead of using > interactive mode. Still need to see if loading a ddp persists on the card > when rebinding the i40e driver instead of vfio / uio. > > The kernel i40e driver also seems to have the functions to use AdminQ to > load DDPs onto the card =E2=80=93 however im not sure how to do it from u= serland. > > > > > > *Von:* Rami Rosen > *Gesendet:* Sonntag, 26. August 2018 20:59 > *An:* sfo@ingenieurbuero-foss.de > *Betreff:* Re: [dts] DDP / testpmd setup > > > > Hi Sebastian, > > I don't know of such a way, unfortunately. Also you cannot automate testp= md > > as it is to load the profile automatically without going interactive mode= . > > > > Regards, > > Rami Rosen > > http://ramirose.wix.com/ramirosen > > > > > > > > > > On Sun, Aug 26, 2018 at 3:18 PM Sebastian Foss > wrote: > > Hi, > > we are using testpmd to store ddp profiles in an Intel X710DA2 NIC. Is > there a way to have those profiles stored in the NIC permanently =E2=80= =93 or what > would be the best solution to have those profiles loaded automatically at > boot and use a regular kernel driver afterwards ? From what i understand = so > far to use the DPDK functions to load a DDP Profile the UIO or VFIO drive= rs > have to be used. > > > > Thank you! > > > > Mit freundlichen Gr=C3=BC=C3=9Fen / Best Regards > > Sebastian Foss, Electrical Engineering (B. Eng.) > > Hardware & Software Development > > Gesch=C3=A4ftsf=C3=BChrer / CEO > > SF Engineering UG & Co. KG > > > > > > > > -- > > regards, > > Rami Rosen > > > > -- > > regards, > > Rami Rosen > --=20 regards, Rami Rosen --0000000000008ac25005747ff0a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Sebastian,
How did you found out it goes= all to queue 0 ? is it by running testpmd in RXonly mode, and setting it t= o verbose
and looking in the content of the packets it shows= on the console=C2=A0 ? or by any other means ?
Also can you= describe your setup - is it with VMs, how do you send the traffic (scapy/p= ktgen/IXIA)?

Regards,
Rami Rosen


On Tue, = Aug 28, 2018 at 5:42 PM Sebastian Foss <sfo@ingenieurbuero-foss.de> wrote:

I used the l= atest pppoe ddp from intel=E2=80=99s website and tried to map/add pctypes 1= 5 and 17 to the hashing =E2=80=93 then run some pppoe when using i40e again= and it still all goes to queue 0.

=C2=A0

testpmd> ddp get in= fo /home/dpdktest/ppp-oe-ol2tpv2.pkgo

Global Track id:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0x80000006

Global Version:=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 1.0.0.0

Gl= obal Package name:=C2=A0=C2=A0 PPPoE and PPPoL2TPv2

=C2=A0

<= span style=3D"font-family:"Calibri",sans-serif;color:black">i40e = Profile Track id: 0x80000006

i40= e Profile Version:=C2=A0 1.0.0.0

i40e Profile name:=C2=A0=C2=A0=C2=A0=C2=A0 E710 PPPoE and PPPoL2TPv2

=C2=A0

Package Notes:

= This= profile enables PPPoE and PPPoL2TPv2 parsing

L2TPv2 Tunnel ID extracted to field 46

L2TPv2/PPPoE Session ID extracted to field 47

PPP Protocol ID extracted to field 48=

=C2=A0

=C2=A0

List of s= upported devices:

=C2=A0 8086:15= 72 FFFF:FFFF

=C2=A0 8086:1574 FF= FF:FFFF

=C2=A0 8086:1580 FFFF:FF= FF

=C2=A0 8086:1581 FFFF:FFFF=

=C2=A0 8086:1583 FFFF:FFFF<= u>

=C2=A0 8086:1584 FFFF:FFFF

=C2=A0 8086:1585 FFFF:FFFF

=C2=A0 8086:1586 FFFF:FFFF

=C2=A0 8086:1587 FFFF:FFFF

=C2=A0 8086:1588 FFFF:FFFF

=C2=A0 8086:1589 FFFF:FFFF

=C2=A0 8086:158A FFFF:FFFF

=C2=A0 8086:158B FFFF:FFFF

= <= /u>=C2=A0

List of used protocols:

=C2=A0 12: IPV4<= /p>

=C2=A0 13: IPV6

=C2=A0 15: GRENAT

=C2=A0 1= 7: TCP

=C2=A0 18: UDP<= /u>

=C2=A0 19: SCTP

=C2=A0 20: ICMP

=C2=A0 22: L2TPv2CTRL

=C2=A0 23= : ICMPV6

=C2=A0 26: L2TPv2

=C2=A0 27: L2TPv2PAY

=C2=A0 28: PPPoL2TPv2

=C2=A0 29: PPPoE

=C2=A0 33: PAY2

=C2=A0 34: PAY= 3

=C2=A0 35: PAY4<= /span>

=C2=A0 44: IPV4FRAG

=C2=A0 48: IPV6FRAG

=C2=A0 52: OIPV4

=C2=A0 53:= OIPV6

=C2=A0

List of defined packet classification types:

=C2=A0 14: L2TPv2CTRL

=C2=A0 15: PPPoE IPV4

<= p class=3D"MsoNormal">=C2=A0 16: PPPoE IPV6

=C2=A0 17: PPPoE

=C2=A0 = 18: PPPoL2TPv2 IPV4

=C2=A0 19: P= PPoL2TPv2 IPV6

=C2=A0 20: PPPo= L2TPv2

=C2=A0 21: L2TPv2PAY

=C2=A0

List of defined packet types:

=C2=A0 154: PPPoE PAY2

=C2=A0 155: PPPoE IPV4FRAG PAY3

=C2=A0 156: PPPoE IPV4 PAY3

= =C2=A0 157: PPPoE IPV4 UDP PAY4

= =C2=A0 158: PPPoE IPV4 TCP PAY4

= =C2=A0 159: PPPoE IPV4 SCTP PAY4

=C2=A0 160: PPPoE IPV4 ICMP PAY4

=C2=A0 161: PPPoE IPV6FRAG PAY3

=C2=A0 162: PPPoE IPV6 PAY3

= =C2=A0 163: PPPoE IPV6 UDP PAY4

= =C2=A0 164: PPPoE IPV6 TCP PAY4

= =C2=A0 165: PPPoE IPV6 SCTP PAY4

=C2=A0 166: PPPoE IPV6 ICMPV6 PAY4

=C2=A0 167: OIPV4 L2TPv2 PPPoL2TPv2 PAY3

=C2=A0 168: OIPV4 L2TPv2 PPPoL2TPv2 IPV4FRAG PAY3

=C2=A0 169: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 PAY= 3

=C2=A0 170: OIPV4 L2TPv2 PPPoL= 2TPv2 IPV4 UDP PAY4

=C2=A0 171: = OIPV4 L2TPv2 PPPoL2TPv2 IPV4 TCP PAY4

=C2=A0 172: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 SCTP PAY4

=C2=A0 173: OIPV4 L2TPv2 PPPoL2TPv2 IPV4 ICMP PAY4=

=C2=A0 174: OIPV4 L2TPv2 PPPoL2= TPv2 IPV6FRAG PAY3

=C2=A0 175: O= IPV4 L2TPv2 PPPoL2TPv2 IPV6 PAY3

=C2=A0 176: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 UDP PAY4

=

=C2=A0 177: OIPV4 L2TPv2 PPPoL2TPv2 IPV6 TCP PAY4=

=C2=A0 178: OIPV4 L2TPv2 PPPoL2TPv2 IP= V6 SCTP PAY4

=C2=A0 179: OIPV4 L= 2TPv2 PPPoL2TPv2 IPV6 ICMPV6 PAY4

=C2=A0 180: OIPV6 L2TPv2 PPPoL2TPv2 PAY3

=C2=A0 181: OIPV6 L2TPv2 PPPoL2TPv2 IPV4FRAG PAY3<= /span>

=C2=A0 182: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 PAY3<= u>

=C2=A0 183: OIPV6 L2TPv2 PPPoL2T= Pv2 IPV4 UDP PAY4

=C2=A0 184: OI= PV6 L2TPv2 PPPoL2TPv2 IPV4 TCP PAY4

=C2=A0 185: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 SCTP PAY4=

=C2=A0 186: OIPV6 L2TPv2 PPPoL2TPv2 IPV4 ICMP PAY4

=C2=A0 187: OIPV6 L2TPv2 PPPoL2TP= v2 IPV6FRAG PAY3

=C2=A0 188: OIP= V6 L2TPv2 PPPoL2TPv2 IPV6 PAY3

= =C2=A0 189: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 UDP PAY4

<= p class=3D"MsoNormal">=C2=A0 190: OIPV6 L2TPv2 PPPoL2TPv2 IPV6 TCP PAY4<= u>

=C2=A0 191: OIPV6 L2TPv2 PPPoL2TPv2 IPV= 6 SCTP PAY4

=C2=A0 150: OIPV6 L2= TPv2 PPPoL2TPv2 IPV6 ICMPV6 PAY4

=C2=A0 12: OIPV4 L2TPv2 L2TPv2CTRL PAY4

=C2=A0 13: OIPV6 L2TPv2 L2TPv2CTRL PAY4

=

=C2=A0 14: OIPV4 L2TPv2 L2TPv2PAY PAY3

=C2=A0 15: OIPV6 L2TPv2 L2TPv2PAY PAY3<= /u>

=C2=A0

Von: Rami Rosen <ramirose@gmail.com>
Gesendet: Dienstag, 28. August 2018 16:38
An: Sebastian Foss <sfo@ingenieurbuero= -foss.de>
Cc: dts@dpdk.org
Betreff: Re: [dts] DDP / testpmd setup<= /u>

=C2=A0

Hi Sebastian,

=C2=A0

W= hat do you get when running:

=C2=A0

testpmd> = ddp get info (profile_path)

=C2=A0

= =C2=A0

On Tue, Aug 28, 2018 at 5= :33 PM Sebastian Foss <sfo@ingenieurbuero-foss.de> wrote:

<= /div>

Hi,

ok seems the dd= p profiles are persistent when unbinding and rebinding the dpdk / linux dri= vers. However it seems like the ddp profile is not used for rss hashing whe= n i bind the i40e driver and run some test (e.g. PPPoE traffic).<= /u>

Are there any plans to support ddp profile= s for rss hashing when i40e is used without dpdk ?

=

=C2=A0

Thanks= .

=C2=A0

Von: Rami Rosen <ramirose@gmail.com>
= Gesendet: Sonntag, 26. August 2018 22:46
An: Sebastian Foss &= lt;sfo@inge= nieurbuero-foss.de>
Cc: dts@dpdk.org
Betreff: Re: [dts] DDP / testpmd= setup

=C2=A0<= /p>

Hi, Sebastian,

Regarding rebinding, there are two types:

=

One is with=C2=A0

=

dpdk-devbind -b i40e pci_id_of_port

And the second is the ribust one:

rmmod i40e and then modpr= obe i40e. I am not sure as to which of the two you aim when talking about r= ebinding.

I would sugges= t to start with the first option. It triggers calling the probe() callback = of I40E, and not the full longer and heavier way with I40E module_exit() an= d module_init() callbacks

=C2=A0

Regarding users= pace app for achieving it: you can follow the dpdk testpmd code, but=

this can take quite a time and= effort.

=C2=A0

Regards,

=

Rami Rosen

=C2=A0

= =C2=A0

=D7=91=D7=AA=D7=90= =D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=9D =D7=90=D7=B3, 26 =D7=91=D7=90=D7=95= =D7=92=D7=B3 2018, 22:57, =D7=9E=D7=90=D7=AA Sebastian Foss =E2=80=8F<sfo@ingenieur= buero-foss.de>:

Hi Rami,

I found t= he switch for testpmd to use a cmd line script instead of using interactive= mode. Still need to see if loading a ddp persists on the card when rebindi= ng the i40e driver instead of vfio / uio.

The kernel i40e driver also seems to have the functions to use A= dminQ to load DDPs onto the card =E2=80=93 however im not sure how to do it= from userland.

=C2=A0

=C2=A0

Von: Rami Rosen <ramirose@gmail.com>
Gesendet:= Sonntag, 26. August 2018 20:59
An: sfo@ingenieurbuero-foss.de
Betreff: Re: [dts] DDP / testpmd setup

=C2=A0

Hi= Sebastian,

I don't = know of such a way, unfortunately. Also you cannot automate testpmd<= u>

as it is to load the profile au= tomatically without going interactive mode.

=C2=A0

Regards,

Rami Rosen

=C2=A0

=C2=A0

=C2=A0

<= /div>

=C2=A0

On Sun, Aug 26, 2018 at 3:18 PM Sebastian Foss <sfo@ingenieurbuero= -foss.de> wrote:

Hi,

we are using= testpmd to store ddp profiles in an Intel X710DA2 NIC. Is there a way to h= ave those profiles stored in the NIC permanently =E2=80=93 or what would be= the best solution to have those profiles loaded automatically at boot and = use a regular kernel driver afterwards ? From what i understand so far to u= se the DPDK functions to load a DDP Profile the UIO or VFIO drivers have to= be used.

=C2=A0

<= p class=3D"MsoNormal">Thank you!

= =C2=A0

= Mit freundlichen Gr=C3=BC=C3=9Fen / Best Regards

Sebastian Foss, Electrical= Engineering (B. Eng.)

Hardware & Software Development=

Gesch=C3=A4ftsf= =C3=BChrer / CEO

SF Engineering UG & Co. KG

=C2=A0=

=C2=A0



--

regards,

Rami Rosen



--

regards,=

Rami Rosen

<= /div>


--
regards,
Rami Rosen
--0000000000008ac25005747ff0a7--