From: Jakub Kicinski <kuba@kernel.org>
To: Sunil Kovvuri Goutham <sgoutham@marvell.com>
Cc: Geethasowjanya Akula <gakula@marvell.com>,
Jiri Pirko <jiri@resnulli.us>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Hariprasad Kelam <hkelam@marvell.com>
Subject: Re: [EXTERNAL] Re: [net-next PATCH v10 00/11] Introduce RVU representors
Date: Thu, 8 Aug 2024 07:40:54 -0700 [thread overview]
Message-ID: <20240808074054.21e7abc6@kernel.org> (raw)
In-Reply-To: <BY3PR18MB473740348BD4FF7241E79C27C6B92@BY3PR18MB4737.namprd18.prod.outlook.com>
On Thu, 8 Aug 2024 11:30:29 +0000 Sunil Kovvuri Goutham wrote:
> >I can't bring myself to apply this.
> >Jiri do you have an opinion?
> >The device is a NPU/SmartNIC/DPU/IPU, it should be very flexible.
> >Yet, instead of just implementing the representors like everyone else you do your
> >own thing and create separate bus devices.
>
> Can you please elaborate what you mean by "create separate bus devices"
You have a separate PF (on top of the existing "AF" PF) which doesn't
have any datapath port of its own.
> Just to clarify we are not creating separate bus devices for representors perse.
> On our HW, there are multiple SRIOV PCI devices.
As in SR-IOV-capable PFs?
> We are using one of those PCI devices (pci/0002:1c:00.0), to attach required hardware resources to it, for doing packet IO
> Between representors and the representees. Once the HW resources (Rx, Tx queues) are attached to it
> we are registering multiple netdevs from this ie one rx/tx queue for one representor.
> Beyond that there are no other bus devices being created/used.
What port is used for communication to the host and the uplink?
We're on v10 and I keep asking for documentation showing the system
topology.
next prev parent reply other threads:[~2024-08-08 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 13:18 [net-next PATCH v10 00/11] Introduce RVU representors Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 01/11] octeontx2-pf: Refactoring RVU driver Geetha sowjanya
2024-08-08 15:41 ` Jiri Pirko
2024-08-16 13:36 ` [EXTERNAL] " Geethasowjanya Akula
2024-08-16 14:10 ` Jiri Pirko
2024-08-20 5:24 ` Geethasowjanya Akula
2024-08-22 14:30 ` Jiri Pirko
2024-09-01 9:52 ` Geethasowjanya Akula
2024-08-05 13:18 ` [net-next PATCH v10 02/11] octeontx2-pf: RVU representor driver Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 03/11] octeontx2-pf: Create representor netdev Geetha sowjanya
2024-08-08 15:51 ` Jiri Pirko
2024-08-16 13:36 ` [EXTERNAL] " Geethasowjanya Akula
2024-08-16 14:12 ` Jiri Pirko
2024-08-20 5:21 ` Geethasowjanya Akula
2024-08-05 13:18 ` [net-next PATCH v10 04/11] octeontx2-pf: Add basic net_device_ops Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 05/11] octeontx2-af: Add packet path between representor and VF Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 06/11] octeontx2-pf: Get VF stats via representor Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 07/11] octeontx2-pf: Add support to sync link state between representor and VFs Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 08/11] octeontx2-pf: Configure VF mtu via representor Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 09/11] octeontx2-pf: Add representors for sdp MAC Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 10/11] octeontx2-pf: Add devlink port support Geetha sowjanya
2024-08-05 13:18 ` [net-next PATCH v10 11/11] octeontx2-pf: Implement offload stats ndo for representors Geetha sowjanya
2024-08-08 2:46 ` [net-next PATCH v10 00/11] Introduce RVU representors Jakub Kicinski
2024-08-08 11:30 ` [EXTERNAL] " Sunil Kovvuri Goutham
2024-08-08 14:40 ` Jakub Kicinski [this message]
2024-08-08 15:46 ` Jiri Pirko
2024-08-16 13:36 ` [EXTERNAL] " Geethasowjanya Akula
2024-08-16 14:17 ` Jiri Pirko
2024-08-20 5:39 ` Geethasowjanya Akula
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=20240808074054.21e7abc6@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@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).