From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pradeep Kumar Nalla <pnalla@marvell.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Satananda Burla <sburla@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 00/15] Octeon Tx/Tx2 Endpoint pmd
Date: Wed, 6 Jan 2021 17:28:11 +0530 [thread overview]
Message-ID: <CALBAE1MNV8Xskn6d30BHzJDsmoeEfS6=t7ZCpqGL+_=Or8rutQ@mail.gmail.com> (raw)
In-Reply-To: <MW2PR18MB2314419FC6CA908C73ADABADC6D09@MW2PR18MB2314.namprd18.prod.outlook.com>
On Wed, Jan 6, 2021 at 5:06 PM Pradeep Kumar Nalla <pnalla@marvell.com> wrote:
>
>
>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Tuesday, January 5, 2021 8:59 PM
> To: Pradeep Kumar Nalla <pnalla@marvell.com>
> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; 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 <ferruh.yigit@intel.com>
> > Sent: Monday, January 4, 2021 5:22 PM
> > To: Pradeep Kumar Nalla <pnalla@marvell.com>
> > Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Satananda Burla
> > <sburla@marvell.com>; 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:
> >> From: "Nalla Pradeep" <pnalla@marvell.com>
> >>
> >> 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.
In other words,
- The net/octeontx2 driver has a separate set of HW devices that are
not accessible from x86 host.
- Even though net/octeontx2 is based on PCI bus, scope of that PCI bus
is internal to SoC. It is an internal bus emulated as PCI to help
standard device probing works.
next prev parent reply other threads:[~2021-01-06 11:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 7:22 [dpdk-dev] " Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 01/15] net/octeontx_ep: add build and doc infrastructure Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 02/15] net/octeontx_ep: add ethdev probe and remove Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 03/15] net/octeontx_ep: add device init and uninit Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 04/15] net/octeontx_ep: Added basic device setup Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 05/15] net/octeontx_ep: Add dev info get and configure Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 06/15] net/octeontx_ep: Added rxq setup and release Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 07/15] net/octeontx_ep: Added tx queue " Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 08/15] net/octeontx_ep: Setting up iq and oq registers Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 09/15] net/octeontx_ep: Added dev start and stop Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 10/15] net/octeontx_ep: Receive data path function added Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 11/15] net/octeontx_ep: Transmit " Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 12/15] net/octeontx_ep: INFO PTR mode support added Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 13/15] net/octeontx_ep: stats get/reset and link update Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 14/15] net/octeontx_ep: rx queue interrupt Nalla, Pradeep
2020-12-31 7:22 ` [dpdk-dev] [PATCH 15/15] net/octeontx_ep: Input output reset Nalla, Pradeep
2021-01-04 11:51 ` [dpdk-dev] [PATCH 00/15] Octeon Tx/Tx2 Endpoint pmd Ferruh Yigit
2021-01-05 14:43 ` [dpdk-dev] [EXT] " Pradeep Kumar Nalla
2021-01-05 15:29 ` Ferruh Yigit
2021-01-06 11:35 ` Pradeep Kumar Nalla
2021-01-06 11:58 ` Jerin Jacob [this message]
2021-01-06 14:24 ` Ferruh Yigit
2021-01-06 14:43 ` Jerin Jacob
2021-01-06 15:30 ` Pradeep Kumar Nalla
2021-01-06 18:13 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALBAE1MNV8Xskn6d30BHzJDsmoeEfS6=t7ZCpqGL+_=Or8rutQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=pnalla@marvell.com \
--cc=sburla@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).