Re: [dpdk-dev] [EXT] Re: [PATCH 00/15] Octeon Tx/Tx2 Endpoint pmd

-----Original Message-----
From: Ferruh Yigit <redacted> 
Sent: Tuesday, January 5, 2021 8:59 PM
To: Pradeep Kumar Nalla <redacted>
Cc: Jerin Jacob Kollanukkaran <redacted>; Satananda Burla <sburla@marvell.com>; dev@dpdk.org
Subject: Re: [EXT] Re: [dpdk-dev] [PATCH 00/15] Octeon Tx/Tx2 Endpoint pmd

On 1/5/2021 2:43 PM, Pradeep Kumar Nalla wrote:

Please do not top post, reply moved below.

Thanks
Pradeep.
-----Original Message-----
From: Ferruh Yigit <redacted>
Sent: Monday, January 4, 2021 5:22 PM
To: Pradeep Kumar Nalla <redacted>
Cc: Jerin Jacob Kollanukkaran <redacted>; Satananda Burla 
[off-list ref]; dev@dpdk.org
Subject: [EXT] Re: [dpdk-dev] [PATCH 00/15] Octeon Tx/Tx2 Endpoint pmd

External Email

----------------------------------------------------------------------
On 12/31/2020 7:22 AM, Nalla, Pradeep wrote:

quoted

From: "Nalla Pradeep" <redacted>

This patch set contains PMD with minimal set of operations that can 
drive both Octeon Tx and Tx2 in endpoint.

Hi Pradeep,

There is already octeontx and octeontx2 net drivers, what is the difference of the 'endpoint' driver, why it is needed, can you please give more information?

Hi Ferruh 

This PMD, while running on a host, drives octeontx/octeontx2 over pci bus, where as "OcteonTx and OcteonTx2 net drivers" run on respective Tx/Tx2 SOCs to make use of h/w blocks present on the SOC.

But aren't they same HW block, either in the SoC or external ethernet controller via PCI bus?

No, this pmd doesn't access any h/w block on the soc. When in ep mode octeontx and octeontx2 present themselves as network devices and this pmd will program that interface and does packet rx/tx.

As far as I can see octeontx2 access the device via PCI bus, why updating the existing driver and adding new device IDs is not working?

OxteonTx2 access H/W blocks on soc which also appear as PCI devices.