from:"Varghese, Vipin"

RE: help

2023-07-25 Thread Varghese, Vipin

[AMD Official Use Only - General]

Like I said earlier, trying with the Intel host I have on VMWARE, specifically  
Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
With IOMMU enabled, VMXNET3 works with VA as well as PA.
[VV] since ` enable_unsafe_iommu: not enabled` on Intel platform, could it be 
possible the specific version EXSI hypervisor supports the HW IOMMU specific to 
the platform. My suspicion will be in case on AMD platform  changes for 
required to enable HW iommu might not be available to specific EXSI (hypervior 
OS) used.

I am not an expert on virtio_user PMD, but I can check if it will work with PA 
with deferred setting for vmx_net3 PMD are ok?

From: Igor de Paula 
Sent: Tuesday, July 25, 2023 8:42 PM
To: Varghese, Vipin 
Cc: Yigit, Ferruh ; Jochen Behrens ; 
Thomas Monjalon ; users@dpdk.org; Gupta, Nipun 
; Agarwal, Nikhil ; Ronak Doshi 
; Immanni, Venkat ; Chenbo Xia 

Subject: Re: help

Caution: This message originated from an External Source. Use proper caution 
when opening attachments, clicking links, or responding.

Well,
Like I said earlier, trying with the Intel host I have on VMWARE, specifically  
Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
With IOMMU enabled, VMXNET3 works with VA as well as PA.
Meaning, PA works regardless if IOMMU is enabled or not. From my experience 
anyway.
That's why I thought that:
virtio_user needs VA to work.
For some reason VMXNET3 does not work with VA (only on AMD host).

On Tue, Jul 25, 2023 at 4:04 PM Varghese, Vipin 
mailto:vipin.vargh...@amd.com>> wrote:

[AMD Official Use Only - General]

Thanks Igor,

As suspected the vmx_net3 works with

  1.  Iommu: disabled
  2.  enable_unsafe_iommu: enabled
  3.  dpdk eal iova mode: PA

as pointed by you in logs, the virtio_user fails as it expects VA too.

Will check and get back.

From: Igor de Paula mailto:igord...@gmail.com>>
Sent: Tuesday, July 25, 2023 8:16 PM
To: Yigit, Ferruh mailto:ferruh.yi...@amd.com>>
Cc: Jochen Behrens mailto:jbehr...@vmware.com>>; Thomas 
Monjalon mailto:tho...@monjalon.net>>; 
users@dpdk.org<mailto:users@dpdk.org>; Gupta, Nipun 
mailto:nipun.gu...@amd.com>>; Agarwal, Nikhil 
mailto:nikhil.agar...@amd.com>>; Ronak Doshi 
mailto:dos...@vmware.com>>; Immanni, Venkat 
mailto:venkat.imma...@amd.com>>; Varghese, Vipin 
mailto:vipin.vargh...@amd.com>>; Chenbo Xia 
mailto:chenbo@intel.com>>
Subject: Re: help

Caution: This message originated from an External Source. Use proper caution 
when opening attachments, clicking links, or responding.

Hi,
Attaching the logs of EAL when trying to run a configuration with virtio_user 
port when IOMMU is
disabled and enable_unsafe_iommu is enabled. As you can see it forces IOVA as 
PA but the viritui_user needs IOVA as VA.
I am also attaching the output of dmesg. I am not sure which kernel logs you 
wanted... if there is anything else please let me know..
Regarding the ESXI logs, they are HUGE so I will send to you on a separate 
email.

On Fri, Jul 21, 2023 at 1:14 PM Ferruh Yigit 
mailto:ferruh.yi...@amd.com>> wrote:
On 7/21/2023 12:39 PM, Igor de Paula wrote:
> I am trying to use virtio_user for an interface with the
> kernel: https://doc.dpdk.org/guides/howto/virtio_user_as_exception_path.html 
> <https://doc.dpdk.org/guides/howto/virtio_user_as_exception_path.html>
> I think this requires IOVA as va.
>

I am not sure if virtio-user has IOVA as VA requirement, cc'ed Chenbo,
he may know better.

Meanwhile can you give a try to 'enable_unsafe_noiommu_mode' and
'--iova-mode=pa'?

> It does work with Intel host and IOMMU
> enabled. Part of the negotiation when setting it up is getting the IOMMU
> number so I thought it has to have IOMMU.
>

Yes, issue looks like related to the IOMMU, and it may be either related
to HW support, or ESXi iommu driver support, we will check using below
information you provided.

> I tried disabling IOMMU and enabling enable_unsafe_noiommu flag but
> again, that didn't work.
> ESXI version - VMware ESXi, 7.0.0, 16324942
> AMD:  AMD EPYC 7452 32-Core Processo
>
> On an Intel host which worked: Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
> Regarding the logs I will try and attach it soon.
>

Thanks for info, waiting for logs.

>
> On Fri, Jul 21, 2023 at 12:21 PM Ferruh Yigit 
> mailto:ferruh.yi...@amd.com>
> <mailto:ferruh.yi...@amd.com<mailto:ferruh.yi...@amd.com>>> wrote:
>
> Hi Igor,
>
> VM doesn't have IOMMU, and vmxnet3 requires PA mode, for this can you
> please try with:
> - enable 'enable_unsafe_noiommu_mode' flag
> - Force PA mode via '--iova-mode=pa' eal parameter
>
>
> Also to be able to figure out AMD IOMMU support level, can you please
> provide:
> - AMD part number
> - ESXi/hypervisor version
> - ESXi & VM kernel logs
>
>
> Thanks,
>

RE: help

2023-07-25 Thread Varghese, Vipin

[AMD Official Use Only - General]

Thanks Igor,

As suspected the vmx_net3 works with


  1.  Iommu: disabled
  2.  enable_unsafe_iommu: enabled
  3.  dpdk eal iova mode: PA

as pointed by you in logs, the virtio_user fails as it expects VA too.

Will check and get back.

From: Igor de Paula 
Sent: Tuesday, July 25, 2023 8:16 PM
To: Yigit, Ferruh 
Cc: Jochen Behrens ; Thomas Monjalon 
; users@dpdk.org; Gupta, Nipun ; 
Agarwal, Nikhil ; Ronak Doshi ; 
Immanni, Venkat ; Varghese, Vipin 
; Chenbo Xia 
Subject: Re: help

Caution: This message originated from an External Source. Use proper caution 
when opening attachments, clicking links, or responding.

Hi,
Attaching the logs of EAL when trying to run a configuration with virtio_user 
port when IOMMU is
disabled and enable_unsafe_iommu is enabled. As you can see it forces IOVA as 
PA but the viritui_user needs IOVA as VA.
I am also attaching the output of dmesg. I am not sure which kernel logs you 
wanted... if there is anything else please let me know..
Regarding the ESXI logs, they are HUGE so I will send to you on a separate 
email.

On Fri, Jul 21, 2023 at 1:14 PM Ferruh Yigit 
mailto:ferruh.yi...@amd.com>> wrote:
On 7/21/2023 12:39 PM, Igor de Paula wrote:
> I am trying to use virtio_user for an interface with the
> kernel: https://doc.dpdk.org/guides/howto/virtio_user_as_exception_path.html 
> <https://doc.dpdk.org/guides/howto/virtio_user_as_exception_path.html>
> I think this requires IOVA as va.
>

I am not sure if virtio-user has IOVA as VA requirement, cc'ed Chenbo,
he may know better.

Meanwhile can you give a try to 'enable_unsafe_noiommu_mode' and
'--iova-mode=pa'?


> It does work with Intel host and IOMMU
> enabled. Part of the negotiation when setting it up is getting the IOMMU
> number so I thought it has to have IOMMU.
>

Yes, issue looks like related to the IOMMU, and it may be either related
to HW support, or ESXi iommu driver support, we will check using below
information you provided.

> I tried disabling IOMMU and enabling enable_unsafe_noiommu flag but
> again, that didn't work.
> ESXI version - VMware ESXi, 7.0.0, 16324942
> AMD:  AMD EPYC 7452 32-Core Processo
>
> On an Intel host which worked: Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
> Regarding the logs I will try and attach it soon.
>

Thanks for info, waiting for logs.

>
> On Fri, Jul 21, 2023 at 12:21 PM Ferruh Yigit 
> mailto:ferruh.yi...@amd.com>
> <mailto:ferruh.yi...@amd.com<mailto:ferruh.yi...@amd.com>>> wrote:
>
> Hi Igor,
>
> VM doesn't have IOMMU, and vmxnet3 requires PA mode, for this can you
> please try with:
> - enable 'enable_unsafe_noiommu_mode' flag
> - Force PA mode via '--iova-mode=pa' eal parameter
>
>
> Also to be able to figure out AMD IOMMU support level, can you please
> provide:
> - AMD part number
> - ESXi/hypervisor version
> - ESXi & VM kernel logs
>
>
> Thanks,
> Ferruh
>
> On 7/20/2023 5:21 PM, Jochen Behrens wrote:
> > +Ronak from the ESX team
> >
> >
> >
> >
> >
> > In our usage, we do set amd_iommu=off in the boot command line from
> > grub. (Or intel_iommu=off for Intel processors.)
> >
> >
> >
> > Jochen
> >
> >
> >
> > *From: *Thomas Monjalon mailto:tho...@monjalon.net>
> <mailto:tho...@monjalon.net<mailto:tho...@monjalon.net>>>
> > *Date: *Thursday, July 20, 2023 at 6:00 AM
> > *To: *Igor de Paula mailto:igord...@gmail.com> 
> <mailto:igord...@gmail.com<mailto:igord...@gmail.com>>>
> > *Cc: *users@dpdk.org<mailto:users@dpdk.org> 
> <mailto:users@dpdk.org<mailto:users@dpdk.org>> 
> mailto:users@dpdk.org>
> <mailto:users@dpdk.org<mailto:users@dpdk.org>>>, Jochen Behrens
> > mailto:jbehr...@vmware.com> 
> <mailto:jbehr...@vmware.com<mailto:jbehr...@vmware.com>>>, Nipun Gupta
> mailto:nipun.gu...@amd.com> 
> <mailto:nipun.gu...@amd.com<mailto:nipun.gu...@amd.com>>>, Nikhil Agarwal
> > mailto:nikhil.agar...@amd.com> 
> <mailto:nikhil.agar...@amd.com<mailto:nikhil.agar...@amd.com>>>, Ferruh
> Yigit mailto:ferruh.yi...@amd.com> 
> <mailto:ferruh.yi...@amd.com<mailto:ferruh.yi...@amd.com>>>
> > *Subject: *Re: help
> >
> > !! External Email
> >
> > +Cc some AMD maintainers, they can have an idea about IOMMU settings.
> >
> >
> > 20/07/2023 14:44, Igor de Paula:
> >> I have enabled it in the host and in the BIOS for AMD...
&g

Re: Issue on capturing using DPDK Pdump on secondary interface

2022-09-23 Thread Varghese, Vipin

[AMD Official Use Only - General]

Hi Srinivas,

Based on the internal testing with dpdk-pdump I do not find the issue with 
PDUMP capture with secondary interface. 
I am able capture for both port0 and port1. Following are the steps I followed

```
cd [dpdk parent folder]
cd app/pdump
gcc main.c $(pkg-config --static --libs --cflags libdpdk) -o mypdump

in terminal 1: start dpdk testpmd "dpdk-testpmd -l 15-16  --vdev=net_tap0 
--vdev=net_tap1 --no-pci -- -i --forward=txonly". Then execute "start" in 
interactive terminal
in terminal 2: start pdump application "./mypdump --no-pci -l 12  -- --pdump 
'port=0,queue=*,tx-dev=/tmp/0.pcap'"
in terminal 3: start pdump application "./mypdump --no-pci -l 13  -- --pdump 
'port=1,queue=*,tx-dev=/tmp/1.pcap'"
```

Stop pdump captures in terminal 2 and 3
Execute on terminal ` tcpdump -nr /tmp/0.pcap`
Execute on terminal ` tcpdump -nr /tmp/1.pcap`

```
# tcpdump -nr /tmp/1.pcap  | more
reading from file /tmp/1.pcap, link-type EN10MB (Ethernet)
23:25:15.682623 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
23:25:15.682625 IP 198.18.0.1.9 > 198.18.0.2.9: UDP, length 22
```

Hence DPDK PDUMP works with second port. I have also tried the same with Intel 
X710 nic too.

note: 
1. are you building DPDK application in shared library mode? If yes please 
ensure for application and dpdk-pdump pass all relevant shared library to init
2. are you passing desired pcie device? Please use dpdk option `-a` to pass the 
interfaces used in primary application for secondary 
3. have you installed pcap-dev library? DPDK pdump makes use of pcap-dev lib to 
write as pcap file. Hence the target should have the library.
4. does the DPDK logs gives any hint? Please re-run both primary and pdump with 
eal option `--log-level=8`

Regards
Vipin Varghese 

> -Original Message-
> From: users-requ...@dpdk.org 
> Sent: Saturday, September 17, 2022 3:30 PM
> To: users@dpdk.org
> Subject: users Digest, Vol 356, Issue 9
> 
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
> 
> 
> Send users mailing list submissions to
> users@dpdk.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail
> s.dpdk.org%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40a
> md.com%7C905f5dbf0db045e968b408da989364df%7C3dd8961fe4884e608e1
> 1a82d994e183d%7C0%7C0%7C637990056071355174%7CUnknown%7CTWFpb
> GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> 6Mn0%3D%7C3000%7C%7C%7Csdata=l0csfydT0085Uztryx%2Bj1mGOy
> 2DS5DIkCfnbMgkOIx8%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org
> 
> You can reach the person managing the list at
> users-ow...@dpdk.org
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
> 
> 
> Today's Topics:
> 
>1. Re: l2fwd: Requested device :02:00.0 cannot be used
>   (Ubuntu 22.04, DPDK 22.07, N5095, I225-V) (Stephen Hemminger)
>2. Re: Issue on capturing using DPDK Pdump on secondary
>   interface. (Stephen Hemminger)
> 
> 
> --
> 
> Message: 1
> Date: Fri, 16 Sep 2022 08:10:59 -0700
> From: Stephen Hemminger 
> To: F32 
> Cc: users@dpdk.org
> Subject: Re: l2fwd: Requested device :02:00.0 cannot be used
> (Ubuntu 22.04, DPDK 22.07, N5095, I225-V)
> Message-ID: <20220916081059.5b9841a1@hermes.local>
> Content-Type: text/plain; charset=US-ASCII
> 
> On Wed, 14 Sep 2022 11:18:11 +0800 (CST)
> F32  wrote:
> 
> > Hi,
> >
> >
> > Recently I'm testing dpdk on a mini PC with N5095 CPU and 5 I225-V
> ethernet adapters under Ubuntu Server 22.04.1.
> >
> >
> > $ uname -r
> > 5.15.0-47-generic
> >
> >
> > $ cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
> > GRUB_CMDLINE_LINUX_DEFAULT="default_hugepagesz=1G
> hugepagesz=1G hugepages=16 intel_iommu=on iommu=pt"
> > $ update-grub
> > $ reboot
> >
> >
> > $ dmesg | grep DMAR
> > [0.016399] ACPI: DMAR 0x787D6000 88 (v02 INTEL  EDK2
> 0002  0113)
> > [0.016443] ACPI: Reserving DMAR table memory at [mem 0x787d6000-
> 0x787d6087]
> > [0.029273] DMAR: IOMMU enabled
> > [0.093267] DMAR: Host address width 39
> > [0.093269] DMAR: DRHD base: 0x00fed9 flags: 0x0
> > [0.093276] DMAR: dmar0: reg_base_addr fed9 ver 4:0 cap
> 1cc40660462 ecap 49e2ff0505e
> > [0.093281] DMAR: DRHD base: 0x00fed91000 flags: 0x1
> > [0.093287] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
> d2008c40660462 ecap f050da
> > [0.093291] DMAR: RMRR base: 0x007b80 end: 0x007fbf
> > [0.093296] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
> > [0.093299] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
> > [0.093301] DMAR-IR: Queued invalidation will be enabled

RE: how to bind VF interface into dpdk (Balakrishnan K)

2022-09-15 Thread Varghese, Vipin

[AMD Official Use Only - General]

Hi Balakrishnan K,

With respect to error (shared below), I believe this is expected 

```
> [ 1394.034137] uio_pci_generic :06:00.0: No IRQ assigned to device: no 
> support for interrupts?
> [ 1394.037596] uio_pci_generic :06:00.0: No IRQ assigned to device: no 
> support for interrupts?
> [ 1421.498627] uio_pci_generic :06:00.0: No IRQ assigned to device: no 
> support for interrupts?
> [ 1421.500976] uio_pci_generic :06:00.0: No IRQ assigned to device: no 
> support for interrupts?
```

Please refer https://doc.dpdk.org/guides/nics/ixgbe.html, section `30.4.5. X550 
does not support legacy interrupt mode`.

With respect to the original error (shared below)

```
> I am trying to bind VF interface to dpdk using dpdk-devbind.py. Unable to 
> bind getting error ?.
```

As per the IXGBE PMD documentation, one has to follow

```
Step-1: insmod ixgbe.ko MDD=0,0
Step-2: PF port is Kernel driver
Step-3: create VF
Step-4: modprobe vfio `` ``nointxmask=1
Step-5: then bind the VF devices with `vfio-pci`
```

For your question ` cannot bind to driver uio_pci_generic?`, I humbly request 
to check ` The errata is the item #22 from X550 spec update` in section ` 
30.4.5.1. Description`. Then check with Intel Network PMD maintainer if this 
can be fixed.

Note: please do let us know if vfio-pci or igb_uio works for VF devices under 
X540 (as I do not have similar card I unable to test it out for you).

> -Original Message-
> From: users-requ...@dpdk.org 
> Sent: Thursday, September 15, 2022 12:42 PM
> To: users@dpdk.org
> Subject: users Digest, Vol 356, Issue 6
> 
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
> 
> 
> Send users mailing list submissions to
> users@dpdk.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail
> s.dpdk.org%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40a
> md.com%7C2ba1c25ba37744b1a16608da96e9a8de%7C3dd8961fe4884e608e1
> 1a82d994e183d%7C0%7C0%7C637988227558550775%7CUnknown%7CTWFpb
> GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> 6Mn0%3D%7C3000%7C%7C%7Csdata=u6aC9rcEHPpC3OCZ6X2ztHj%2F
> NXJQQfEG6626NHpHohk%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org
> 
> You can reach the person managing the list at
> users-ow...@dpdk.org
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
> 
> 
> Today's Topics:
> 
>1. RE: how to bind VF interface into dpdk (Balakrishnan K)
> 
> 
> --
> 
> Message: 1
> Date: Thu, 15 Sep 2022 07:12:18 +
> From: Balakrishnan K 
> To: Satish Patel 
> Cc: "users@dpdk.org" 
> Subject: RE: how to bind VF interface into dpdk
> Message-ID:
> 
>  4.prod.outlook.com>
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Sathish,
>   Thanks for the input .
> Checked the dmesg  below are the error msg.
> [ 1394.034137] uio_pci_generic :06:00.0: No IRQ assigned to device: no
> support for interrupts?
> [ 1394.037596] uio_pci_generic :06:00.0: No IRQ assigned to device: no
> support for interrupts?
> [ 1421.498627] uio_pci_generic :06:00.0: No IRQ assigned to device: no
> support for interrupts?
> [ 1421.500976] uio_pci_generic :06:00.0: No IRQ assigned to device: no
> support for interrupts?
> 
> Is any BIOS setting needed to resolve the issue.
> 
> 
> Regards,
> Bala
> 
> 
> 
> From: Satish Patel 
> Sent: 15 September 2022 08:00
> To: Balakrishnan K 
> Cc: users@dpdk.org
> Subject: Re: how to bind VF interface into dpdk
> 
> 
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
> Hi,
> 
>  I would also check dmesg logs for any indication or warning. I had an issue
> like that and it turned out to be a BIOS setting related to some nic shared
> memory.
> 
> On Wed, Sep 14, 2022 at 8:30 AM Balakrishnan K
> mailto:Balakrishnan.K1@tataco
> mmunications.com>> wrote:
> Hi All,
> I am trying to bind VF interface to dpdk using dpdk-devbind.py.
> Unable to bind getting error ?cannot bind to driver uio_pci_generic?.
> Steps followed:
> 1.modprobe uio_pci_generic
> 2. dpdk-devbind.py -b uio_pci_generic :05:00.0
> 
> Also tried with vfio-pci driver not succeeded.
> Attaching the dpdk-devbind -s output and the error which I got.
> 
> Am I missing something could any one please help on this.
> 
> [cid:image001.png@01D8C900.9517D660]
> 
> [cid:image002.png@01D8C900.9517D660]
> 
> Regards,
> Bala
> -- next part --
> An HTML attachment was scrubbed...
> URL:
>

Re: skeleton code failing (Lokesh Chakka)

2022-08-28 Thread Varghese, Vipin

Hi Lokesh,

Based on the DPDK logs, following are some of the observations

1. application is built with shared library mode ` gcc main.c -g `pkg-config 
--cflags libdpdk --libs libdpdk` which may require to pass shared dpdk PMD 
library with option `-d` in eal args
2. EAL PCIe probe identified `:83:00.0` and `:83:00.1`
3. there is warning from application on core NUMA-Socket vs NIC NUMA-Socket for 
the DPDK ports ` WARNING, port 0 is on remote NUMA node to polling thread. 
Performance will not be optimal. WARNING, port 1 is on remote NUMA node to 
polling thread. Performance will not be optimal.`
4. application has started on CPU logical thread 0 and waiting for user to 
interrupt the same ` Core 0 forwarding packets. [Ctrl+C to quit]`

With these observations the application is running with DPDK ports. 

With respect to queries
1. surprisingly cards are not showing up even in ifconfig - Braodcom NIC card 
(PF or VF) when bind with DPDK get removed from from kernel `bxnt` and added to 
`igb_uio|vfio_pci|uio_pci_generic`. This means there is no kernel netlink 
device attached to the NIC port.
2. dpdk-pmdinfo.py ./a.out But I am not seeing any output - as mentioned above 
this could be because the application is linked in shared library mode.
3. `gcc main.c `pkg-config --cflags libdpdk --libs libdpdk` Hence it is 
statically linked code. - this understanding is incorrect as the command to 
link statically is `pkg-config --static --cflags --libs libdpdk`.
4. Unlike other examples like l2fwd, l3fwd, testpmd there is procedure or call 
to function to display PMD stats for NIC ports

Hence, I recommend to spent some time 
https://doc.dpdk.org/guides/sample_app_ug/skeleton.html and then 
1. if the intention is build with static library, use the right command to to 
built the application.
2. Do not expect Broadcom NIC to make both Kernel netlink and DPDK available at 
the same time for PCIe id.
3. Use `log-level=pmd,8` to get more PMD related information.
4. Send traffic DPDK ports, and use `dpdk-procinfo` with option `--stats` to 
get the stats via DPDK secondary app.

Note: It could be NIC related issue you have to reach out Broadcom as NIC 
vendor for your current use case.

Regards
Vipin Varghese 

> -Original Message-
> From: users-requ...@dpdk.org 
> Sent: Friday, August 26, 2022 3:30 PM
> To: users@dpdk.org
> Subject: users Digest, Vol 353, Issue 5
> 
> [CAUTION: External Email]
> 
> Send users mailing list submissions to
> users@dpdk.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail
> s.dpdk.org%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40a
> md.com%7C3b2eb0cad85d4133795e08da8749bf40%7C3dd8961fe4884e608e1
> 1a82d994e183d%7C0%7C0%7C637971048067638133%7CUnknown%7CTWFpb
> GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> 6Mn0%3D%7C3000%7C%7C%7Csdata=WhU4xEpP2iZ8T3fp%2BKZjhGr4
> 47C6PUh5kRMAeNKNUyU%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org
> 
> You can reach the person managing the list at
> users-ow...@dpdk.org
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
> 
> 
> Today's Topics:
> 
>1. DPD-22.07 bind error=-19 (sysman@scaled.cloud)
>2. Re: skeleton code failing (Lokesh Chakka)
> 
> 
> --
> 
> Message: 1
> Date: Thu, 25 Aug 2022 13:50:16 +0300
> From: sysman@scaled.cloud
> To: users@dpdk.org
> Subject: DPD-22.07 bind error=-19
> Message-ID: 
> Content-Type: text/plain; charset=US-ASCII; format=flowed
> 
> Hello All!
> 
>   Can someone help me to resolved situation:
> 
> ubuntu 20 lts
> dpdk 22-0
> 
> 
> root@noserve1:/home/user/Works/tootoo2# dpdk-devbind.py -s
> 
> Network devices using kernel driver
> ===
> :05:00.0 'I211 Gigabit Network Connection 1539' if=enp5s0 drv=igb
> unused=vfio-pci,uio_pci_generic *Active*
> :06:00.0 'I211 Gigabit Network Connection 1539' if=enp6s0 drv=igb
> unused=vfio-pci,uio_pci_generic
> :07:00.0 'I211 Gigabit Network Connection 1539' if=enp7s0 drv=igb
> unused=vfio-pci,uio_pci_generic
> :08:00.0 'I211 Gigabit Network Connection 1539' if=enp8s0 drv=igb
> unused=vfio-pci,uio_pci_generic
> :09:00.0 'I211 Gigabit Network Connection 1539' if=enp9s0 drv=igb
> unused=vfio-pci,uio_pci_generic
> :0a:00.0 'I211 Gigabit Network Connection 1539' if=enp10s0 drv=igb
> unused=vfio-pci,uio_pci_generic
> 
> Other Network devices
> =
> :01:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572'
> unused=i40e,vfio-pci,uio_pci_generic
> :01:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572'
> unused=i40e,vfio-pci,uio_pci_generic
> :01:00.2 'Ethernet Controller X710 for 10GbE SFP+ 1572'
> unused=i40e,vfio-pci,uio_pci_generic
> :01:00.3 'Ethernet

RE: Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)

2022-07-18 Thread Varghese, Vipin

[Public]

As pointed out application vice skeleton is better than l2fwd as it uses 
tx_burst over tx_buffer. With respect to NIC you will need to investigate how 
the PMD driver supports low latency (1 RX burst) and which firmware to use.

Note:
1. Based on my internal testing done I do find tx_buffer vs tx_buffer different.
2. Intel E810 does support low_latency mode via PMD args

From: Usman Tanveer 
Sent: Monday, July 18, 2022 3:55 PM
To: Varghese, Vipin 
Cc: users@dpdk.org
Subject: Re: Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)

[CAUTION: External Email]
DPDK example L@FWD uses TX_BUFFER, which internally accumulates `n` packets 
then send to device to amortize the cost. So my suggestion is not to use DPDK 
L2fwd for latency test. Instead make use of DPDK example SKELETON which 
directly uses `tx_burst`.

I have tried SKELETON with BURST_SIZE = 1, it also shows the same behavior i.e. 
packets are being accumulated.

On Sat, Jul 16, 2022 at 10:39 AM Varghese, Vipin 
mailto:vipin.vargh...@amd.com>> wrote:
[AMD Official Use Only - General]

DPDK example L@FWD uses TX_BUFFER, which internally accumulates `n` packets 
then send to device to amortize the cost. So my suggestion is not to use DPDK 
L2fwd for latency test. Instead make use of DPDK example SKELETON which 
directly uses `tx_burst`.

> -Original Message-
> From: users-requ...@dpdk.org<mailto:users-requ...@dpdk.org> 
> mailto:users-requ...@dpdk.org>>
> Sent: Friday, July 15, 2022 3:30 PM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: users Digest, Vol 347, Issue 13
>
> [CAUTION: External Email]
>
> Send users mailing list submissions to
> users@dpdk.org<mailto:users@dpdk.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp%2F=05%7C01%7CVipin.Varghese%40amd.com%7Ccfaae67b9ab84021723008da68a7c928%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637937367101285256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=A%2FTmIH3LG7hkjpMWRcziQpUPnMnVVoLIOWRR0HudeY0%3D=0>
> dk.org<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.org%2F=05%7C01%7CVipin.Varghese%40amd.com%7Ccfaae67b9ab84021723008da68a7c928%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637937367101285256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hsweuVLDPaRQpxbCX0rzdvSsydwG1KpT38Rk3UOUjSM%3D=0>%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40amd.co<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2F40amd.co%2F=05%7C01%7CVipin.Varghese%40amd.com%7Ccfaae67b9ab84021723008da68a7c928%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637937367101285256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=Ge3nPMUcisvGAeAhU3ecE63ewUnXq0rXAYHntyJiXuw%3D=0>
> m%7Cbe1da1e5c9884d626f9f08da6648ca0f%7C3dd8961fe4884e608e11a82d99
> 4e183d%7C0%7C0%7C637934760074138757%7CUnknown%7CTWFpbGZsb3d8e
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C3000%7C%7C%7Csdata=mF6VDr1GkGr3L13V7aplaxY58dHXpvdxcmqjj
> a%2Ba3kQ%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org<mailto:users-requ...@dpdk.org>
>
> You can reach the person managing the list at
> users-ow...@dpdk.org<mailto:users-ow...@dpdk.org>
>
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
>
>
> Today's Topics:
>
>1. Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)
>2. mlx5: Keeping packets with invalid CRC/FCS (Pfau, Johannes (ITIV))
>
>
> --
>
> Message: 1
> Date: Thu, 14 Jul 2022 16:39:54 +0500
> From: Usman Tanveer 
> mailto:usman.tanv...@emumba.com>>
> To: users@dpdk.org<mailto:users@dpdk.org>
> Cc: shsha...@marvell.com<mailto:shsha...@marvell.com>, 
> rm...@marvell.com<mailto:rm...@marvell.com>
> Subject: Packet Accumulation in RX and TX in bnx2x
> Message-ID:
>  77rDV+n6crq14T=p1h...@mail.gmail.com<mailto:p1h...@mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I have a *BroadCom NetXtreme II BCM57810 10 Gigabit *with a *bnx2x*
> driver.
> I was trying to measure the performance of the network card. I'm running
> DPDK-L2FWD application to receive and send packets with MAX_PKT_BURST =
> 1.
> but I noticed that packets are being accumulated somewhere in bnx2x_rxtx.
> There is some sort of batching/buffe

Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)

2022-07-15 Thread Varghese, Vipin

[AMD Official Use Only - General]

DPDK example L@FWD uses TX_BUFFER, which internally accumulates `n` packets 
then send to device to amortize the cost. So my suggestion is not to use DPDK 
L2fwd for latency test. Instead make use of DPDK example SKELETON which 
directly uses `tx_burst`.

> -Original Message-
> From: users-requ...@dpdk.org 
> Sent: Friday, July 15, 2022 3:30 PM
> To: users@dpdk.org
> Subject: users Digest, Vol 347, Issue 13
> 
> [CAUTION: External Email]
> 
> Send users mailing list submissions to
> users@dpdk.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp
> dk.org%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40amd.co
> m%7Cbe1da1e5c9884d626f9f08da6648ca0f%7C3dd8961fe4884e608e11a82d99
> 4e183d%7C0%7C0%7C637934760074138757%7CUnknown%7CTWFpbGZsb3d8e
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C3000%7C%7C%7Csdata=mF6VDr1GkGr3L13V7aplaxY58dHXpvdxcmqjj
> a%2Ba3kQ%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org
> 
> You can reach the person managing the list at
> users-ow...@dpdk.org
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
> 
> 
> Today's Topics:
> 
>1. Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)
>2. mlx5: Keeping packets with invalid CRC/FCS (Pfau, Johannes (ITIV))
> 
> 
> --
> 
> Message: 1
> Date: Thu, 14 Jul 2022 16:39:54 +0500
> From: Usman Tanveer 
> To: users@dpdk.org
> Cc: shsha...@marvell.com, rm...@marvell.com
> Subject: Packet Accumulation in RX and TX in bnx2x
> Message-ID:
>  77rDV+n6crq14T=p1h...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi,
> 
> I have a *BroadCom NetXtreme II BCM57810 10 Gigabit *with a *bnx2x*
> driver.
> I was trying to measure the performance of the network card. I'm running
> DPDK-L2FWD application to receive and send packets with MAX_PKT_BURST =
> 1.
> but I noticed that packets are being accumulated somewhere in bnx2x_rxtx.
> There is some sort of batching/buffering happening in rxtx. So, the latency of
> the packets is increasing as they have to wait.
> The first packet of the batch is received with the minimum latency and
> incoming packets are received with the accumulated latency of the previous
> packets. After a specific number of packets (6-7 packets), the same pattern
> repeats i.e. a packet arrives with the minimum latency and incoming packets
> with accumulated latency until the specific number of packets arrives. I've
> copied the latency measured for some contiguous packets.
> 
> I tried to explore bnx2x_recv_pkts() and bnx2x_xmit_pkts() in bnx2x_rxtx.c, 
> but
> didn't get any clue why the packets were being accumulated.
> 
> Sequence Latency (microseconds)
> 4825105 9.37207
> 4825106 10.72168
> 4825107 15.06543
> 4825108 19.394043
> 4825109 22.665039
> 4825110 26.979004
> 4825111 8.74707
> 4825112 11.145996
> 4825113 14.439941
> 4825114 18.701172
> 4825115 23.082031
> 4825116 27.402832
> 4825117 9.164062
> 4825118 11.623047
> 4825119 15.944824
> 4825120 19.066406
> 4825121 23.589355
> 4825122 27.909668
> 4825123 9.701172
> 4825124 11.13916
> 4825125 15.489746
> 4825126 19.780762
> 4825127 23.111816
> 4825128 27.403809
> -- next part --
> An HTML attachment was scrubbed...
> URL:
>  dk.org%2Farchives%2Fusers%2Fattachments%2F20220714%2F6887b7b4%2Fatt
> achment-
> 0001.htmdata=05%7C01%7Cvipin.varghese%40amd.com%7Cbe1da1e5c
> 9884d626f9f08da6648ca0f%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C
> 0%7C637934760074138757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C
> %7Csdata=ICLtgULJ6%2BTmatMiSECKtf0HTESOyd25TOzkygF%2FUsA%3D
> reserved=0>
> 
> --
> 
> Message: 2
> Date: Thu, 14 Jul 2022 13:52:14 +
> From: "Pfau, Johannes (ITIV)" 
> To: "users@dpdk.org" 
> Subject: mlx5: Keeping packets with invalid CRC/FCS
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi all,
> 
> We're currently developing a low-cost DAQ system to record high-bandwidth
> data from FPGA systems. We're using DPDK with Mellanox Connect-X5 cards,
> the drivers and DPDK installed from the standard RHEL 8 repositories. We
> capture raw ethernet (no L3) on 1:1 links to the FPGA devices to avoid all
> possible overhead. So far this setup works great, we can handle 100 Gbit/s of
> traffic even on a single core, but we can also distribute packets to multiple
> cores depending on the ether type if required.
> 
> To save a few more bits in the transmission, we'd like to avoid encoding 
> packet
> counters into the data stream. In that case we have to make sure we never
> miss

RE: skeleton code failing (Lokesh Chakka)

2022-07-14 Thread Varghese, Vipin

[Public]

[LC] I am having is 
https://www.broadcom.com/products/ethernet-connectivity/network-adapters/p2100g<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.broadcom.com%2Fproducts%2Fethernet-connectivity%2Fnetwork-adapters%2Fp2100g=05%7C01%7CVipin.Varghese%40amd.com%7C255e189a10194e84dab008da656a11ed%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933803507082842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=GInrRYkg8qTsJ02CbjPSl%2FLT6C4cJ4Yt2fMkNfGmFho%3D=0>
 However, cards are up after waiting for around 10 minutes.

[VV] I do face similar issue, hence I have recommended ` Observation: due some 
hardware or firmware bug auto-neg take more time with the current DPDK BXNT 
PMD. Hence my advice is try to wait longer for link state up in DPDK.`. Please 
try reaching out to Broadcom PMD maintainer `ajit.khapa...@broadcom.com`. Once 
the solution is identified please share too


[LC] If netdevice is not available, how can I capture the packets using 
wireshark?
[VV] Please explore DPDK tool PDUMP. 
https://doc.dpdk.org/guides/tools/pdump.html

[LC] Interfaces are not visible to the wireshark. Very basic requirement is to 
send the packets, capture them and see the contents.
[VV] If you want the kernel netdev visible and use it under DPDK, I recommend 
using LIBPCAP PMD by sacrificing performance and higher functionality.

From: Lokesh Chakka 
Sent: Thursday, July 14, 2022 12:56 PM
To: Varghese, Vipin 
Cc: users@dpdk.org; Yigit, Ferruh ; Tummala, Sivaprasad 

Subject: Re: skeleton code failing (Lokesh Chakka)

[CAUTION: External Email]

The card I am having is 
https://www.broadcom.com/products/ethernet-connectivity/network-adapters/p2100g<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.broadcom.com%2Fproducts%2Fethernet-connectivity%2Fnetwork-adapters%2Fp2100g=05%7C01%7CVipin.Varghese%40amd.com%7C255e189a10194e84dab008da656a11ed%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933803507082842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=GInrRYkg8qTsJ02CbjPSl%2FLT6C4cJ4Yt2fMkNfGmFho%3D=0>
However, cards are up after waiting for around 10 minutes.

Thanks for the valuable input. skeleton code is running till I press ctrl+c.
Now I have a big concern.
If netdevice is not available, how can I capture the packets using wireshark?
Interfaces are not visible to the wireshark. Very basic requirement is to send 
the packets, capture them and see the contents.


Thanks & Regards
--
Lokesh Chakka.


On Thu, Jul 14, 2022 at 11:46 AM Varghese, Vipin 
mailto:vipin.vargh...@amd.com>> wrote:

[AMD Official Use Only - General]

Is this not Broadcom extreme net card? Please refer 
http://doc.dpdk.org/guides/nics/bnxt.html<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Fnics%2Fbnxt.html=05%7C01%7CVipin.Varghese%40amd.com%7C255e189a10194e84dab008da656a11ed%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933803507082842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=qsqUSFyPvnm%2Frqqy5RkOfMu2WREnXXNPAoQNrBb09ig%3D=0>,
 once you bind with `igb_uio, vfio_pci or uio_pci_generic` all linux netdevice 
instance will be no longer available. This is because it is not a `port 
representator`

Observation: due some hardware or firmware bug auto-neg take more time with the 
current DPDK BXNT PMD. Hence my advice is try to wait longer for link state up 
in DPDK.
You can verify the same with testpmd.

From: Lokesh Chakka 
mailto:lvenkatakumarcha...@gmail.com>>
Sent: Thursday, July 14, 2022 11:11 AM
To: Varghese, Vipin mailto:vipin.vargh...@amd.com>>
Cc: users@dpdk.org<mailto:users@dpdk.org>; Yigit, Ferruh 
mailto:ferruh.yi...@amd.com>>; Tummala, Sivaprasad 
mailto:sivaprasad.tumm...@amd.com>>
Subject: Re: skeleton code failing (Lokesh Chakka)

[CAUTION: External Email]
I have one more observation here.
After "$ sudo dpdk-devbind.py -b vfio-pci 83:00.0 83:00.1"

Cards are shutting down. ifconfig is not showing the cards. reinsert of sfp is 
also not bringing the cards up. I had to restart the server. Not sure why the 
cards are going down.

Thanks & Regards
--
Lokesh Chakka.


On Thu, Jul 14, 2022 at 8:50 AM Varghese, Vipin 
mailto:vipin.vargh...@amd.com>> wrote:
[AMD Official Use Only - General]

Based on the compilation command shared it looks like you are using the build 
in shared library mode ` gcc main.c -g `pkg-config --cflags libdpdk --libs 
libdpdk`
Hence in EAL PCIe probe, the BNXT PMD is not triggered to identify the NIC.

Solutions for these can be
1. Build with static library ` gcc main.c -g `pkg-config --cflags libdpdk 
--libs --static libdpdk`
2. pass the bxnt_en PMD shared library to eal args by ` sudo ./a.out -l 1 -d 
librte_net_bnxt.so`

Can you try any of the above ?

> -O

RE: skeleton code failing (Lokesh Chakka)

2022-07-14 Thread Varghese, Vipin

[AMD Official Use Only - General]

Is this not Broadcom extreme net card? Please refer 
http://doc.dpdk.org/guides/nics/bnxt.html, once you bind with `igb_uio, 
vfio_pci or uio_pci_generic` all linux netdevice instance will be no longer 
available. This is because it is not a `port representator`

Observation: due some hardware or firmware bug auto-neg take more time with the 
current DPDK BXNT PMD. Hence my advice is try to wait longer for link state up 
in DPDK.
You can verify the same with testpmd.

From: Lokesh Chakka 
Sent: Thursday, July 14, 2022 11:11 AM
To: Varghese, Vipin 
Cc: users@dpdk.org; Yigit, Ferruh ; Tummala, Sivaprasad 

Subject: Re: skeleton code failing (Lokesh Chakka)

[CAUTION: External Email]
I have one more observation here.
After "$ sudo dpdk-devbind.py -b vfio-pci 83:00.0 83:00.1"

Cards are shutting down. ifconfig is not showing the cards. reinsert of sfp is 
also not bringing the cards up. I had to restart the server. Not sure why the 
cards are going down.

Thanks & Regards
--
Lokesh Chakka.


On Thu, Jul 14, 2022 at 8:50 AM Varghese, Vipin 
mailto:vipin.vargh...@amd.com>> wrote:
[AMD Official Use Only - General]

Based on the compilation command shared it looks like you are using the build 
in shared library mode ` gcc main.c -g `pkg-config --cflags libdpdk --libs 
libdpdk`
Hence in EAL PCIe probe, the BNXT PMD is not triggered to identify the NIC.

Solutions for these can be
1. Build with static library ` gcc main.c -g `pkg-config --cflags libdpdk 
--libs --static libdpdk`
2. pass the bxnt_en PMD shared library to eal args by ` sudo ./a.out -l 1 -d 
librte_net_bnxt.so`

Can you try any of the above ?

> -Original Message-
> From: users-requ...@dpdk.org<mailto:users-requ...@dpdk.org> 
> mailto:users-requ...@dpdk.org>>
> Sent: Wednesday, July 13, 2022 3:30 PM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: users Digest, Vol 347, Issue 6
>
> [CAUTION: External Email]
>
> Send users mailing list submissions to
> users@dpdk.org<mailto:users@dpdk.org>
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp%2F=05%7C01%7CVipin.Varghese%40amd.com%7C4b323bb32c214497ef5e08da655b7693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933740761659125%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=kEjFmF8PaxwPyIXKcpB1B9VJjuLzzFqB5zl3Ahmd%2BAs%3D=0>
> dk.org<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.org%2F=05%7C01%7CVipin.Varghese%40amd.com%7C4b323bb32c214497ef5e08da655b7693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933740761659125%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=0zrwvV24mjHlR9qLiLsL9cUHePu%2B4l2mr9iTfFYQRyI%3D=0>%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40amd.co<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2F40amd.co%2F=05%7C01%7CVipin.Varghese%40amd.com%7C4b323bb32c214497ef5e08da655b7693%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933740761659125%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rlZbwJ5OkgTUEgS2pPROwbYV9VhtuQDxSgrOrRIP9FQ%3D=0>
> m%7C55465d0d4faa4cd8496a08da64b674f4%7C3dd8961fe4884e608e11a82d9
> 94e183d%7C0%7C0%7C637933032067208770%7CUnknown%7CTWFpbGZsb3d8
> eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C3000%7C%7C%7Csdata=6JHjf2Fu%2BkQ56CF9xTZvBS%2Bh8Uomlqv
> E9dq9M7VefiU%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org<mailto:users-requ...@dpdk.org>
>
> You can reach the person managing the list at
> users-ow...@dpdk.org<mailto:users-ow...@dpdk.org>
>
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
>
>
> Today's Topics:
>
>1. Re: skeleton code failing (Lokesh Chakka)
>
>
> --
>
> Message: 1
> Date: Wed, 13 Jul 2022 12:56:37 +0530
> From: Lokesh Chakka 
> mailto:lvenkatakumarcha...@gmail.com>>
> To: David Marchand 
> mailto:david.march...@redhat.com>>
> Cc: users mailto:users@dpdk.org>>
> Subject: Re: skeleton code failing
> Message-ID:
>  nm_pwq59fy9qvnh+gbg...@mail.gmail.com<mailto:nm_pwq59fy9qvnh%2bgbg...@mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Dear David,
>
> following is some more stuff i did
> ==
> $ sudo dpdk-devbind.py -b vfio-pci 83:00.0 $ sudo dpdk

Re: skeleton code failing (Lokesh Chakka)

2022-07-13 Thread Varghese, Vipin

[AMD Official Use Only - General]

Based on the compilation command shared it looks like you are using the build 
in shared library mode ` gcc main.c -g `pkg-config --cflags libdpdk --libs 
libdpdk`
Hence in EAL PCIe probe, the BNXT PMD is not triggered to identify the NIC. 

Solutions for these can be
1. Build with static library ` gcc main.c -g `pkg-config --cflags libdpdk 
--libs --static libdpdk`
2. pass the bxnt_en PMD shared library to eal args by ` sudo ./a.out -l 1 -d 
librte_net_bnxt.so`

Can you try any of the above ?

> -Original Message-
> From: users-requ...@dpdk.org 
> Sent: Wednesday, July 13, 2022 3:30 PM
> To: users@dpdk.org
> Subject: users Digest, Vol 347, Issue 6
> 
> [CAUTION: External Email]
> 
> Send users mailing list submissions to
> users@dpdk.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp
> dk.org%2Flistinfo%2Fusersdata=05%7C01%7Cvipin.varghese%40amd.co
> m%7C55465d0d4faa4cd8496a08da64b674f4%7C3dd8961fe4884e608e11a82d9
> 94e183d%7C0%7C0%7C637933032067208770%7CUnknown%7CTWFpbGZsb3d8
> eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C3000%7C%7C%7Csdata=6JHjf2Fu%2BkQ56CF9xTZvBS%2Bh8Uomlqv
> E9dq9M7VefiU%3Dreserved=0
> or, via email, send a message with subject or body 'help' to
> users-requ...@dpdk.org
> 
> You can reach the person managing the list at
> users-ow...@dpdk.org
> 
> When replying, please edit your Subject line so it is more specific than "Re:
> Contents of users digest..."
> 
> 
> Today's Topics:
> 
>1. Re: skeleton code failing (Lokesh Chakka)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 13 Jul 2022 12:56:37 +0530
> From: Lokesh Chakka 
> To: David Marchand 
> Cc: users 
> Subject: Re: skeleton code failing
> Message-ID:
>  nm_pwq59fy9qvnh+gbg...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Dear David,
> 
> following is some more stuff i did
> ==
> $ sudo dpdk-devbind.py -b vfio-pci 83:00.0 $ sudo dpdk-devbind.py -b vfio-pci
> 83:00.1 $ sudo dpdk-devbind.py -b uio_pci_generic 83:00.0 83:00.1
> Error: Driver 'uio_pci_generic' is not loaded.
> $ sudo dpdk-devbind.py -b igb_uio 83:00.0 83:00.1
> Error: Driver 'igb_uio' is not loaded.
> $ sudo dpdk-devbind.py -b vfio-pci 83:00.0 83:00.1
> Notice: :83:00.0 already bound to driver vfio-pci, skipping
> Notice: :83:00.1 already bound to driver vfio-pci, skipping
> ==
> ~/Desktop/dpdk_examples/skeleton$ gcc main.c -g `pkg-config --cflags libdpdk
> --libs libdpdk` lokesh@lokesh-ProLiant-DL385-
> Gen10:~/Desktop/dpdk_examples/skeleton$ sudo ./a.out
> EAL: Detected CPU lcores: 64
> EAL: Detected NUMA nodes: 4
> EAL: Detected shared linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'VA'
> EAL: No available 1048576 kB hugepages reported
> EAL: VFIO support initialized
> EAL: Using IOMMU type 1 (Type 1)
> EAL: Probe PCI driver: net_bnxt (14e4:1750) device: :83:00.0 (socket 2)
> EAL: Probe PCI driver: net_bnxt (14e4:1750) device: :83:00.1 (socket 2)
> TELEMETRY: No legacy callbacks, legacy socket not created Port 0 MAC: bc 97
> e1 ce 84 f0 Port 1 MAC: bc 97 e1 ce 84 f1
> 
> WARNING: Too many lcores enabled. Only 1 used.
> WARNING, port 0 is on remote NUMA node to polling thread.
> Performance will not be optimal.
> WARNING, port 1 is on remote NUMA node to polling thread.
> Performance will not be optimal.
> 
> Core 0 forwarding packets. [Ctrl+C to quit] ^C
> ==
> After a few seconds, I presses ctrl+c
> 
> surprisingly cards are not showing up even in ifconfig.
> 
> 
> 
> Thanks & Regards
> --
> Lokesh Chakka.
> 
> 
> On Wed, Jul 13, 2022 at 12:43 PM Lokesh Chakka <
> lvenkatakumarcha...@gmail.com> wrote:
> 
> > Dear David,
> >
> > =
> > $ lspci | grep -i broadcom
> > 83:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57508
> > NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11)
> > 83:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57508
> > NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11) $ lspci
> > -n -s 83:00.0
> > 83:00.0 0200: 14e4:1750 (rev 11)
> > =
> >
> > I am compiling my code like this :
> > =
> > gcc main.c `pkg-config --cflags libdpdk --libs libdpdk`
> > =
> >
> > Hence it is statically linked code.
> > If I try
> > $ dpdk-pmdinfo.py ./a.out
> >
> > But I am not seeing any output
> >
> >
> >
> > Thanks & Regards
> > --
> > Lokesh Chakka.
> >
> >
> > On Wed, Jul 13, 2022 at 12:22 PM David Marchand
> > 
> > wrote:
> >
> >> On Wed, Jul

Re: [dpdk-users] users Digest, Vol 293, Issue 3

2021-06-17 Thread Varghese, Vipin

HI Amir Hossein, 



> Message: 1
> Date: Wed, 16 Jun 2021 17:23:22 +0430
> From: Amir Hossein <1377amirhossein1...@gmail.com>
> To: users@dpdk.org
> Subject: [dpdk-users] rte_flow_validate failure with error-38
> Message-ID:
>eo60v4...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> Hi all,
> 
> I'm trying to run flow_filtering sample application, but
> rte_flow_validate(...) return value is -38 and I can't find more information 
> about
> this error code.
> 
> The only change i made is changing nr_queues to 4.(it seems number of rx
> queues should be power of 2 in vmxnet3)
> 
> Is it about hardware support?any help would be appreciated.

As far I recollect VMXNET3 did not support RTE_FLOW. One can verify this from 
driver code or looking into `Table 1.2 rte_flow items availability in 
networking drivers` in http://doc.dpdk.org/guides/nics/overview.html

> 
> I'm using dpdk-stable-19.11.8(target=x86_64-native-linuxapp-gcc) and my nic is
> vmxnet3.
> 
> (error:
> 
> Flow can't be created 1 message: Function not implemented
> EAL: Error - exiting with code: 1

Hence the error message is correct.

> 
> )
> 
> Regards,
> 
> Amir
>

Re: [dpdk-users] [dpdk-dev] DPDK issue with Marvell NIC QLogic Corp. FastLinQ QL41000

2021-05-26 Thread Varghese, Vipin

Based on the logs shared from `Turing Team`, the observation is as follows

1. 1GB huge pages are used in the application

```logs
12:46:11.792 §EAL: No free hugepages reported in hugepages-2048kB
12:46:11.792 §EAL: No available hugepages reported in hugepages-2048kB
```

2. Issue comes right at `device porbe to initialize`

```logs
12:46:46.382 §EAL: Probe PCI driver: net_qede (1077:8070) device: :65:00.0 
(socket 0)
12:46:46.403 §[QEDE PMD: ()]ecore_load_mcp_offsets:The address of the MCP 
scratch-pad is not configured
12:46:46.403 §[QEDE PMD: ()]ecore_mcp_cmd_init:MCP is not initialized
12:46:46.404 §[QEDE PMD: ()]ecore_mcp_cmd_and_union:MFW is not initialized!
12:46:46.404 §[QEDE PMD: ()]ecore_hw_get_nvm_info:Shared memory not initialized
12:46:46.404 §[QEDE PMD: ()]ecore_hw_prepare_single:Failed to get HW information
12:46:46.404 §[qed_probe:74(65:00.0:dpdk-port-0)]hw prepare failed
12:46:46.404 §[qede_common_dev_init:2566(65:00.0:dpdk-port-> 0)]qede probe 
failed rc -3
```

Hence in my opinion this is related to NIC in use and how it is getting 
initialized. So please try to debug driver 

> -Original Message-
> From: dev  On Behalf Of Truring Team
> Sent: Wednesday, May 26, 2021 10:12 AM
> To: Nishant Verma 
> Cc: d...@dpdk.org; USERS 
> Subject: Re: [dpdk-dev] [dpdk-users] DPDK issue with Marvell NIC QLogic
> Corp. FastLinQ QL41000
> 
> Yes , I have configured it via grub.
> 
> Grub:
> "default_hugepagesz=1G hugepagesz=1G hugepages=2"
> grub2-mkconfig -o /boot/grub2/grub.cfg
> 
> Manual:
> mkdir /dev/hugepages1G
> mount -t hugetlbfs -o pagesize=1G none /dev/hugepages1G echo 2 >
> /sys/devices/system/node/node1/hugepages/hugepages-
> 1048576kB/nr_hugepages
> 
> Regards
> Puneet
> 
> On Wed, 26 May 2021 at 10:05, Nishant Verma  wrote:
> 
> > meminfo states: Hugepagesize:1048576 kB
> > But  in your initial mail you state Hugepage size is 1G.
> >
> > have you configured HugePage via grub ?
> >
> >
> > Thanks.
> >
> > Regards,
> > NV
> >
> > On Wed, May 26, 2021 at 12:21 AM Truring Team 
> wrote:
> >
> >> Hi Nishant,
> >>
> >> cat /proc/meminfo
> >> 11:59:29.200 §MemTotal:   23101672 kB
> >> 11:59:29.200 §MemFree:15254764 kB
> >> 11:59:29.200 §MemAvailable:   19243184 kB
> >> 11:59:29.200 §Buffers:6792 kB
> >> 11:59:29.201 §Cached:  4084844 kB
> >> 11:59:29.201 §SwapCached:0 kB
> >> 11:59:29.201 §Active:  3609016 kB
> >> 11:59:29.201 §Inactive:1175160 kB
> >> 11:59:29.201 §Active(anon): 695644 kB
> >> 11:59:29.202 §Inactive(anon):19716 kB
> >> 11:59:29.202 §Active(file):2913372 kB
> >> 11:59:29.202 §Inactive(file):  1155444 kB
> >> 11:59:29.202 §Unevictable:   0 kB
> >> 11:59:29.202 §Mlocked:   0 kB
> >> 11:59:29.203 §SwapTotal:  11665404 kB
> >> 11:59:29.204 §SwapFree:   11665404 kB
> >> 11:59:29.204 §Dirty:32 kB
> >> 11:59:29.204 §Writeback: 0 kB
> >> 11:59:29.204 §AnonPages:694764 kB
> >> 11:59:29.205 §Mapped:   140220 kB
> >> 11:59:29.205 §Shmem: 22800 kB
> >> 11:59:29.205 §Slab: 445016 kB
> >> 11:59:29.205 §SReclaimable: 289968 kB
> >> 11:59:29.205 §SUnreclaim:   155048 kB
> >> 11:59:29.206 §KernelStack:   16624 kB
> >> 11:59:29.206 §PageTables:35892 kB
> >> 11:59:29.206 §NFS_Unstable:  0 kB
> >> 11:59:29.206 §Bounce:0 kB
> >> 11:59:29.206 §WritebackTmp:  0 kB
> >> 11:59:29.207 §CommitLimit:22167664 kB
> >> 11:59:29.207 §Committed_AS:4342668 kB
> >> 11:59:29.207 §VmallocTotal:   34359738367 kB
> >> 11:59:29.207 §VmallocUsed:  463188 kB
> >> 11:59:29.207 §VmallocChunk:   34358835196 kB
> >> 11:59:29.208 §HardwareCorrupted: 0 kB
> >> 11:59:29.208 §AnonHugePages:329728 kB
> >> 11:59:29.208 §CmaTotal:  0 kB
> >> 11:59:29.209 §CmaFree:   0 kB
> >> 11:59:29.209 §HugePages_Total:1024
> >> 11:59:29.209 §HugePages_Free: 1019
> >> 11:59:29.209 §HugePages_Rsvd:0
> >> 11:59:29.209 §HugePages_Surp:0
> >> 11:59:29.209 §Hugepagesize:   2048 kB
> >> 11:59:29.209 §DirectMap4k:  381760 kB
> >> 11:59:29.209 §DirectMap2M:13973504 kB
> >> 11:59:29.215 §DirectMap1G:11534336 kB
> >>
> >> Regards
> >>
> >>
> >> On Wed, 26 May 2021 at 09:43, Nishant Verma 
> wrote:
> >>
> >>> Can you paste output of /proc/meminfo ?
> >>>
> >>>
> >>>
> >>> Regards,
> >>> NV
> >>>
> >>> On Tue, May 25, 2021 at 9:52 PM Truring Team 
> >>> wrote:
> >>>
>  Hi Team,
> 
>  I am trying to run the dpdk test-pmd application (DPDK 20.11 and
>  DPDK
>  21.05) with NIC QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE
>  Controller but facing following issues:
> 
>  If someone can look into the following logs and help me figure out
>  the issue?
> 
> 
> 
>  1. DPDK 20.11 ( Using 1 GB hugepages)
> 
> gdb ./dpdk-testpmd
> 
>  12:45:59.347 §GNU gdb (GDB) Red Hat

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

2020-07-29 Thread Varghese, Vipin

Hi Dikshant,

Summarizing the contents from earlier mails below

1. Issue-1 shared with PDUMP not working with testpmd - solution shared and 
suggested what needs to be added to fix the same.

2. Issue-2 shared for custom Makefile for application not working - pointed out 
possible cause and missing order of libraries in CFLAGS and LDFLAGS. Suggested 
to use an existing working DPDK/example content for custom Makefile. 

Please note I do not have the project or Makefile for use case to try it 
locally, hence please try

```
5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-lrte_pdump`

Hint: I normally take up sample like example/l2fwd and work towards to removing 
unwanted libraries while keeping the content and format intact for my custom 
makefile.
```

Snipped

> 
> Hi Vipin,
> 
> Here is full log with include option and build with make -n option from master
> makefile as well:
> 
> make[2]: Entering directory
> `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKE
> T_GENERATOR'
> echo ./packet_generator.cc  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Module_API/-
> I../../../COMMON/Sys_API/common_intel/
> echo packet_generator.o
> test -d  || mkdir -p
> g++  -msse4.1  -I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Math_API/  -
> I../../../COMMON/Sys_API/Module_API -I./ -
> DTIME_DATE=\"DATE:29/07/20_TIME:09:57:19\" -
> DMOD_NAME=\"PACKET_GENERATOR_TEST_MOD\"  -DARCH_X86 -
> I/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/include
> -I -DAS_INFRA_NULL=0 -DEMULATOR_MODE  -DINTEL -std=c++11  -D_4x4_ -O3
> -g -DDEBUG   -fPIC -c ./packet_generator.cc
> echo
> /usr/local/include:/opt/intel/system_studio_2019/compilers_and_libraries_20
> 19.2.187/linux/pstl/include:/opt/intel/system_studio_2019/compilers_and_lib
> raries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compiler
> s_and_libraries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019
> /compilers_and_libraries_2019.2.187/linux/ipp/include:/opt/intel/system_stu
> dio_2019/compilers_and_libraries_2019.2.187/linux/mkl/include:/opt/intel/s
> ystem_studio_2019/compilers_and_libraries_2019.2.187/linux/ipp/include:/o
> pt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/linux/mkl/i
> nclude:/opt/intel/system_studio_2019/compilers_and_libraries_2019.2.187/li
> nux/pstl/include:/opt/intel/system_studio_2019/compilers_and_libraries_201
> 9.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers_and_libr
> aries_2019.2.187/linux/tbb/include:/opt/intel/system_studio_2019/compilers
> _and_libraries_2019.2.187/linux/daal/include
> echo packet_generator.o
> test -d ../../../COMMON/../bin || mkdir -p ../../../COMMON/../bin
> g++ -shared -Wl,--export-dynamic packet_generator.o
> g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/li
> g++ b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> g++ -Wl,-lrte_eventdev -Wl,-lpcap -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl
> g++ -Wl,--end-group -Wl,--no-whole-archive  -o
> g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> make[2]: Leaving directory
> `/mnt/data/dchitkara/PHY5G/Prototype/NR_5G_SIM/Tests/COMMON/PACKE
> T_GENERATOR'
> 
> Please have a note that module we are running is just one part of our CPP
> project treated as a separate test module.

snipped
> 
> Hi Dikshant,
> 
> Looks like the custom Makefile log is quite different in passing DPDK CFLAGS
> and LDFLAGS. Also here are couple of surprises for me
> 
> 1. Unable to find `make -n` logs
> 
> 2. presence of g++ is present in each line
> 
> 3. unable to find include option
> 
> 4. request was to run `make -n` and cross the relevant libraries are bound
> within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `.
> 
> 5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-
> lrte_pdump`
> 
> Hint: I normally take up sample like example/l2fwd and work towards to
> removing unwanted libraries while keeping the content and format intact for
> my custom makefile.
> 
snipped

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

2020-07-29 Thread Varghese, Vipin

Couple more request, 

1. please avoid ` NOT FROM AIRSPAN - Caution - External ` headers & banners.

2. If possible, use `snip` or `snipped` to remove clutter and bring foucs

Snipped

> Hi Dikshant,
> 
> Looks like the custom Makefile log is quite different in passing DPDK CFLAGS
> and LDFLAGS. Also here are couple of surprises for me
> 
> 1. Unable to find `make -n` logs
> 
> 2. presence of g++ is present in each line
> 
> 3. unable to find include option
> 
> 4. request was to run `make -n` and cross the relevant libraries are bound
> within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `.
> 
> 5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-
> lrte_pdump`
> 
> Hint: I normally take up sample like example/l2fwd and work towards to
> removing unwanted libraries while keeping the content and format intact for
> my custom makefile.
> 
snipped
> >
> > Hi Vipin,
> >
> > I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `
> > option with my necessary libraries but it does not seem to help as well.
> >
> > Below is the makefile log for my app:
> >
> > g++ -shared -Wl,--export-dynamic packet_generator.o
> > g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/
> > g++ li b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> > g++ -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> > g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> > g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> > g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> > g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> > g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> > g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> > g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> > g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> > g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> > g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> > g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> > g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> > g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm
> > g++ -Wl,-ldl -Wl,--end-group -Wl,--no-whole-archive  -o
> > g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> >
> >
snipped
> >
> > > Hi Team,
> > >
> > > With fix suggest in prev mail thread at testpmd side, PDUMP works
> > > with testpmd.
> > >
> > > However when we try to run our own primary app with PDUMP as a
> > > secondary process, PDUMP console comes up, however it does not
> > > capture
> > any packets.
> > >
> > > Changes made at primary app side:
> > > 1. PDUMP initialised just after rte eal init:
> > >
> > >   ret_pdump = rte_pdump_init();
> > >if (ret_pdump < 0) {
> > >printf("rte_pdump_init failed\n");
> > >}
> > >else
> > >{
> > >printf("rte_pdump_init success\n");
> > >}
> > >
> > > 2. Makefile modified to add all relevant files to be linked:
> > >
> > > LIB_SO =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> > > lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool
> > > -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring
> > > -lrte_member  -
> > lrte_eventdev  -
> > > lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> > > lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline
> > > -lrte_table -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm
> > > -lrte_power -lrte_acl  -lrte_meter  -lrte_sch
> > >
> > > Even tried to link final DPDK lib so as well:
> > > LIB_SO =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-
> archive -
> > > L/usr/lib/x86_64-linux-gnu/ -fPIC
> >
> > Ok, I think I have seen similar outcomes in custom Makefiles. Can you
> > execute with `make -n` with the master Makefile and cross the
> > necessary libraries are in bound between `-Wl,--whole-archive` and
> > `-Wl,--no-whole-archive ` (specically for shared libraries).
> >
> > snipped

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

2020-07-29 Thread Varghese, Vipin

Hi Dikshant,

Looks like the custom Makefile log is quite different in passing DPDK CFLAGS 
and LDFLAGS. Also here are couple of surprises for me 

1. Unable to find `make -n` logs

2. presence of g++ is present in each line

3. unable to find include option

4. request was to run `make -n` and cross the relevant libraries are bound 
within the `-Wl,--whole-archive` and `-Wl,--no-whole-archive `. 

5. Unable to find `-Wl,-lpcap` passed for `-Wl,-lrte_pmd_pcap -Wl,-lrte_pdump`

Hint: I normally take up sample like example/l2fwd and work towards to removing 
unwanted libraries while keeping the content and format intact for my custom 
makefile. 

> -Original Message-
> From: Dikshant Chitkara 
> Sent: Wednesday, July 29, 2020 2:44 PM
> To: Varghese, Vipin ; Stephen Hemminger
> 
> Cc: users@dpdk.org; d...@dpdk.org; Amir Ilan ; Veeresh
> Patil 
> Subject: RE: [dpdk-dev] DPDK PDUMP Issue
> 
> Hi Vipin,
> 
> I tried using `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  option with
> my necessary libraries but it does not seem to help as well.
> 
> Below is the makefile log for my app:
> 
> g++ -shared -Wl,--export-dynamic packet_generator.o
> g++ -L/mnt/data/dchitkara/DPDK_2020_01_30_x86/x86_64-native-linux-icc/li
> g++ b -Wl,--whole-archive -Wl,-lrte_mempool_ring -Wl,-lrte_member
> g++ -Wl,-lrte_eventdev -Wl,-lrte_pmd_pcap -Wl,-lrte_pdump
> g++ -Wl,-lrte_bus_vmbus -Wl,-lrte_pci -Wl,-lrte_bus_pci
> g++ -Wl,-lrte_bus_vdev -Wl,-lrte_net -Wl,-lrte_distributor
> g++ -Wl,-lrte_reorder -Wl,-lrte_kni -Wl,-lrte_pipeline -Wl,-lrte_table
> g++ -Wl,-lrte_port -Wl,-lrte_timer -Wl,-lrte_hash -Wl,-lrte_jobstats
> g++ -Wl,-lrte_lpm -Wl,-lrte_power -Wl,-lrte_acl -Wl,-lrte_meter
> g++ -Wl,-lrte_sched -Wl,-lm -Wl,-lrt -Wl,-lrte_vhost -Wl,--start-group
> g++ -Wl,-lrte_kvargs -Wl,-lrte_mbuf -Wl,-lrte_ip_frag -Wl,-lrte_ethdev
> g++ -Wl,-lrte_cryptodev -Wl,-lrte_mempool -Wl,-lrte_ring -Wl,-lrte_eal
> g++ -Wl,-lrte_cmdline -Wl,-lrte_cfgfile -Wl,-lrte_pmd_bond
> g++ -Wl,-lrte_pmd_vmxnet3_uio -Wl,-lrte_pmd_virtio -Wl,-lrte_pmd_cxgbe
> g++ -Wl,-lrte_pmd_enic -Wl,-lrte_pmd_i40e -Wl,-lrte_pmd_fm10k
> g++ -Wl,-lrte_pmd_ixgbe -Wl,-lrte_pmd_e1000 -Wl,-lrte_pmd_ring
> g++ -Wl,-lrte_pmd_af_packet -Wl,-lrte_pmd_null -Wl,-lrt -Wl,-lm -Wl,-ldl
> g++ -Wl,--end-group -Wl,--no-whole-archive  -o
> g++ ../../../COMMON/../bin/PACKET_GENERATOR_TEST_MOD.so
> 
> 
> Thanks,
> Dikshant
> 
> Snipped
> 
> > Hi Team,
> >
> > With fix suggest in prev mail thread at testpmd side, PDUMP works with
> > testpmd.
> >
> > However when we try to run our own primary app with PDUMP as a
> > secondary process, PDUMP console comes up, however it does not capture
> any packets.
> >
> > Changes made at primary app side:
> > 1. PDUMP initialised just after rte eal init:
> >
> >   ret_pdump = rte_pdump_init();
> >if (ret_pdump < 0) {
> >printf("rte_pdump_init failed\n");
> >}
> >else
> >{
> >printf("rte_pdump_init success\n");
> >}
> >
> > 2. Makefile modified to add all relevant files to be linked:
> >
> > LIB_SO =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> > lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool
> > -lrte_cryptodev -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -
> lrte_eventdev  -
> > lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> > lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline -lrte_table
> > -lrte_timer  - lrte_hash  -lrte_jobstats  -lrte_lpm -lrte_power
> > -lrte_acl  -lrte_meter  -lrte_sch
> >
> > Even tried to link final DPDK lib so as well:
> > LIB_SO =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive 
> > -
> > L/usr/lib/x86_64-linux-gnu/ -fPIC
> 
> Ok, I think I have seen similar outcomes in custom Makefiles. Can you execute
> with `make -n` with the master Makefile and cross the necessary libraries are
> in bound between `-Wl,--whole-archive` and `-Wl,--no-whole-archive `
> (specically for shared libraries).
> 
> snipped

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

2020-07-28 Thread Varghese, Vipin

Snipped

> Hi Team,
> 
> With fix suggest in prev mail thread at testpmd side, PDUMP works with
> testpmd.
> 
> However when we try to run our own primary app with PDUMP as a secondary
> process, PDUMP console comes up, however it does not capture any packets.
> 
> Changes made at primary app side:
> 1. PDUMP initialised just after rte eal init:
> 
>   ret_pdump = rte_pdump_init();
>if (ret_pdump < 0) {
>printf("rte_pdump_init failed\n");
>}
>else
>{
>printf("rte_pdump_init success\n");
>}
> 
> 2. Makefile modified to add all relevant files to be linked:
> 
> LIB_SO =-L$(DPDK_LIB) -lrte_mbuf -lrte_eal -lnuma -lrte_pmd_pcap -
> lrte_pdump  -lrte_pmd_i40e -lrte_eal -lrte_ring -lrte_mempool -lrte_cryptodev
> -lrte_ethdev -lrte_mbuf -lrte_mempool_ring  -lrte_member  -lrte_eventdev  -
> lrte_bus_vmbus   -lrte_pci  -lrte_bus_pci  -lrte_bus_vdev  -lrte_net  -
> lrte_distributor  -lrte_reorder  -lrte_kni  -lrte_pipeline  -lrte_table  
> -lrte_timer  -
> lrte_hash  -lrte_jobstats  -lrte_lpm  -lrte_power  -lrte_acl  -lrte_meter  
> -lrte_sch
> 
> Even tried to link final DPDK lib so as well:
> LIB_SO =-L$(DPDK_LIB) -Wl,--whole-archive -ldpdk -Wl,--no-whole-archive -
> L/usr/lib/x86_64-linux-gnu/ -fPIC

Ok, I think I have seen similar outcomes in custom Makefiles. Can you execute 
with `make -n` with the master Makefile and cross the necessary libraries are 
in bound between `-Wl,--whole-archive` and `-Wl,--no-whole-archive `  
(specically for shared libraries). 

snipped

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

2020-07-21 Thread Varghese, Vipin

Snipped

> Dikshant Chitkara  wrote:
> 
> > Hi Team,
> >
> > We are facing an issue w.r.t to using DPDK PDUMP utility and want to check 
> > if
> you can help us in this regard.
> >
> > This issue is specific to DPDK 19.05 version or may  be newer versions and
> was not found on DPDK 18.08 version.
> >
> > The issue is that when we built DPDK in shared library mode and try to run
> PDUMP we get following error on PDUMP console:
> >
> > EAL: Failed to hotplug add device
> > EAL: Error - exiting with code: 1
> >   Cause: vdev creation failed
> >
> > On Debugging above error message, I found that inside rte_dev_probe()
> function in the file  lib/librte_eal/common/eal_common_dev.c , req.result = -
> 14 which is non-zero value and points to enum EFAULT (Bad address) value,
> thus leading to above error.
> >
> > However, when I ran PDUMP in DPDK 18.08, I did not observe any such issue
> and it worked fine.
> >
> > DPDK was built with following flags set in config/common_base file:
> >
> > CONFIG_RTE_LIBRTE_PMD_PCAP=y
> > CONFIG_RTE_LIBRTE_PDUMP=y
> >
> > I ran PDUMP with testpmd as primary application and was trying to send
> some traffic on the Ethernet dpdk port using testpmd and capture it using
> pdump.
> >
> > Attached are the logs for both testpmd and pdump in both DPDK19_05 and
> DPDK_18_08 version for your reference.
> >
> > Let us know if you can help in this regard.
> >
> > Thanks,
> > Dikshant
> >
> 
> Pdump runs as secondary process, what is your primary process.
> Is the secondary process using the same exact versions of DPDK and libraries 
> as
> the primary process?
> The secondary process needs access to the same devices and drivers as the
> primary process to work.

Based on the log files shared, I have made assumptions as

1. Primary: testpmd
2. DPDK version: 19.05
3. SHARED LIB in .config: yes
4. export LD_LIBRARY_PATH: yes

Using arguments passed in primary, I faced error
```
EAL: Error - exiting with code: 1
  Cause: Creation of mbuf pool for socket 0 failed: Invalid argument

  Cause: Mempool creation failed: Invalid argument
```

Hence had to modify with ` -d librte_mempool_ring.so`.  Using arguments passed 
in secondary, I faced similar error too. 

With these corrections, I am able to get similar error shared as
```
EAL: failed to parse device "vdev:net_pcap_tx_0"
EAL: Failed to hotplug add device on primary
EAL: Error - exiting with code: 1
  Cause: vdev creation failed
```

Checking the testpmd Makefile, it is narrowed down to missing PCAP_PMD build 
factor. I rebuild testpmd with ` LD_FLAGS="-lrte_pmd_pcap" make` and re-ran the 
same. With this I can get it working properly. 

Ideally there should had been an entry in Makefile as 
```
ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
LDLIBS += -lrte_pmd_pcap
endif
```

reference: This is similar to the error and solution provided in ` 
https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotplug-add-device/62869287#62869287`

RE: help

RE: help

Re: Issue on capturing using DPDK Pdump on secondary interface

RE: how to bind VF interface into dpdk (Balakrishnan K)

Re: skeleton code failing (Lokesh Chakka)

RE: Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)

Packet Accumulation in RX and TX in bnx2x (Usman Tanveer)

RE: skeleton code failing (Lokesh Chakka)

RE: skeleton code failing (Lokesh Chakka)

Re: skeleton code failing (Lokesh Chakka)

Re: [dpdk-users] users Digest, Vol 293, Issue 3

Re: [dpdk-users] [dpdk-dev] DPDK issue with Marvell NIC QLogic Corp. FastLinQ QL41000

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

Re: [dpdk-users] [dpdk-dev] DPDK PDUMP Issue

17 matches

Site Navigation

Mail list logo

Footer information