Received-SPF: pass (google.com: domain of linux-kernel+bounces-199849-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 3 Jun 2024 16:54:03 -0700
From: Jakub Kicinski <kuba@kernel.org>
To: Yojana Mallik <y-mallik@ti.com>
Cc: Andrew Lunn <andrew@lunn.ch>, schnelle@linux.ibm.com,
 wsa+renesas@sang-engineering.com, diogo.ivo@siemens.com,
 rdunlap@infradead.org, horms@kernel.org, vigneshr@ti.com, rogerq@ti.com,
 danishanwar@ti.com, pabeni@redhat.com, edumazet@google.com,
 davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
 srk@ti.com, rogerq@kernel.org
Subject: Re: [PATCH net-next v2 0/3] Introducing Intercore Virtual Ethernet
 (ICVE) driver
Message-ID: <20240603165403.1133217c@kernel.org>
In-Reply-To: <8f5d2448-bfd7-48a5-be12-fb16cdc4de79@lunn.ch>
References: <20240531064006.1223417-1-y-mallik@ti.com>
	<8f5d2448-bfd7-48a5-be12-fb16cdc4de79@lunn.ch>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sun, 2 Jun 2024 17:45:29 +0200 Andrew Lunn wrote:
> On Fri, May 31, 2024 at 12:10:03PM +0530, Yojana Mallik wrote:
> > virtio-net provides a solution for virtual ethernet interface in a
> > virtualized environment.
> > 
> > There might be a use-case for traffic tunneling between heterogeneous
> > processors in a non virtualized environment such as TI's AM64x that has
> > Cortex A53 and Cortex R5 where Linux runs on A53 and a flavour of RTOS
> > on R5(FreeRTOS) and the ethernet controller is managed by R5 and needs
> > to pass some low priority data to A53.
> > 
> > One solution for such an use case where the ethernet controller does
> > not support DMA for Tx/Rx channel, could be a RPMsg based shared memory
> > ethernet driver.  
> 
> virtio-net is very generic and vendor agnostic.
> 
> Looking at icve, what is TI specific? Why not define a generic
> solution which could be used for any heterogeneous system? We are
> seeming more and more such systems, and there is no point everybody
> re-inventing the wheel. So what i would like to see is something
> similar to driver/tty/rpmsg_tty.c, a driver/net/ethernet/rpmsg_eth.c,
> with good documentation of the protocol used, so that others can
> implement it. And since you say you have FreeRTOS on the other end,
> you could also contribute that side to FreeRTOS as well. A complete
> open source solution everybody can use.

100% agreed! FWIW there's also a PCIe NTB driver which provides very
similar functionality.