On Wed, 30 Apr 2025 at 22:21, Stephen Hemminger
wrote:
> On Wed, 30 Apr 2025 22:00:29 +0530
> Prashant Upadhyaya wrote:
>
> > On Wed, 30 Apr 2025 at 19:58, Stephen Hemminger <
> step...@networkplumber.org>
> > wrote:
> >
> > > On Wed, 30 Apr 2025 13:00:53 +0530
> > > Prashant Upadhyaya wrote:
>
On Wed, 30 Apr 2025 22:00:29 +0530
Prashant Upadhyaya wrote:
> On Wed, 30 Apr 2025 at 19:58, Stephen Hemminger
> wrote:
>
> > On Wed, 30 Apr 2025 13:00:53 +0530
> > Prashant Upadhyaya wrote:
> >
> > > > With DPDK on Azure, an application should never use the VF directly.
> > > > It needs to
On Wed, 30 Apr 2025 at 19:58, Stephen Hemminger
wrote:
> On Wed, 30 Apr 2025 13:00:53 +0530
> Prashant Upadhyaya wrote:
>
> > > With DPDK on Azure, an application should never use the VF directly.
> > > It needs to use either netvsc PMD which handles both the vmbus (slow
> path)
> > > and VF (fa
On Wed, 30 Apr 2025 13:00:53 +0530
Prashant Upadhyaya wrote:
> > With DPDK on Azure, an application should never use the VF directly.
> > It needs to use either netvsc PMD which handles both the vmbus (slow path)
> > and VF (fast path) combined. Or use the older vdev_netvsc/failsafe/tap
> > combi
On Tue, 29 Apr 2025 at 21:54, Stephen Hemminger
wrote:
> On Tue, 29 Apr 2025 21:45:36 +0530
> Prashant Upadhyaya wrote:
>
> > On Mon, 28 Apr 2025 at 21:07, Stephen Hemminger <
> step...@networkplumber.org>
> > wrote:
> >
> > > On Mon, 28 Apr 2025 11:31:10 +0530
> > > Prashant Upadhyaya wrote:
>
On Tue, 29 Apr 2025 21:45:36 +0530
Prashant Upadhyaya wrote:
> On Mon, 28 Apr 2025 at 21:07, Stephen Hemminger
> wrote:
>
> > On Mon, 28 Apr 2025 11:31:10 +0530
> > Prashant Upadhyaya wrote:
> >
> > > On Sat, 26 Apr 2025 at 20:58, Stephen Hemminger <
> > step...@networkplumber.org>
> > > wro
On Mon, 28 Apr 2025 at 21:07, Stephen Hemminger
wrote:
> On Mon, 28 Apr 2025 11:31:10 +0530
> Prashant Upadhyaya wrote:
>
> > On Sat, 26 Apr 2025 at 20:58, Stephen Hemminger <
> step...@networkplumber.org>
> > wrote:
> >
> > > On Fri, 25 Apr 2025 23:17:30 +0530
> > > Prashant Upadhyaya wrote:
>
On Mon, 28 Apr 2025 11:31:10 +0530
Prashant Upadhyaya wrote:
> On Sat, 26 Apr 2025 at 20:58, Stephen Hemminger
> wrote:
>
> > On Fri, 25 Apr 2025 23:17:30 +0530
> > Prashant Upadhyaya wrote:
> >
> > > Hi,
> > >
> > > I am having a VM on Azure where I have got two 'accelerated networking'
> >
On Sat, 26 Apr 2025 at 20:58, Stephen Hemminger
wrote:
> On Fri, 25 Apr 2025 23:17:30 +0530
> Prashant Upadhyaya wrote:
>
> > Hi,
> >
> > I am having a VM on Azure where I have got two 'accelerated networking'
> > interfaces of Mellanox
> > # lspci -nn|grep -i ether
> > 6561:00:02.0 Ethernet con
On Fri, 25 Apr 2025 23:17:30 +0530
Prashant Upadhyaya wrote:
> Hi,
>
> I am having a VM on Azure where I have got two 'accelerated networking'
> interfaces of Mellanox
> # lspci -nn|grep -i ether
> 6561:00:02.0 Ethernet controller [0200]: Mellanox Technologies MT27710
> Family [ConnectX-4 Lx Vir
Short answer Accelerated networking on Azure is not designed to support
bifurcated VF usage
On Fri, Apr 25, 2025, 10:47 Prashant Upadhyaya
wrote:
> Hi,
>
> I am having a VM on Azure where I have got two 'accelerated networking'
> interfaces of Mellanox
> # lspci -nn|grep -i ether
> 6561:00:02.0
Hi,
I am having a VM on Azure where I have got two 'accelerated networking'
interfaces of Mellanox
# lspci -nn|grep -i ether
6561:00:02.0 Ethernet controller [0200]: Mellanox Technologies MT27710
Family [ConnectX-4 Lx Virtual Function] [15b3:1016] (rev 80)
f08c:00:02.0 Ethernet controller [0200]:
12 matches
Mail list logo