On 10/17/2023 5:43 PM, Stephen Hemminger wrote:
> On Tue, 15 Feb 2022 22:16:28 +0530
> Vipul Ashri wrote:
>
>> On 2/14/2022 10:24 PM, Stephen Hemminger wrote:
>>> On Mon, 14 Feb 2022 13:09:19 +
>>> Vipul Ashri wrote:
>>>
PORT 0 supports 16 rx queues and 16 tx queues (driver_name = net
On Tue, 15 Feb 2022 22:16:28 +0530
Vipul Ashri wrote:
> On 2/14/2022 10:24 PM, Stephen Hemminger wrote:
> > On Mon, 14 Feb 2022 13:09:19 +
> > Vipul Ashri wrote:
> >
> >> PORT 0 supports 16 rx queues and 16 tx queues (driver_name = net_failsafe,
> >> driver_type = 16)
> >>
> >> PORT 0 is
On 2/15/2022 4:24 PM, Vipul Ashri wrote:
> On 11/22/2021 3:53 PM, Gaëtan Rivet wrote:
>> Could describe in more detail the execution?
>> In particular, setting the EAL log-level to debug with the option:
>> ' --log-level pmd.net.failsafe:debug '
>> for example while using testpmd or your DPDK app.
On 2/14/2022 10:24 PM, Stephen Hemminger wrote:
On Mon, 14 Feb 2022 13:09:19 +
Vipul Ashri wrote:
PORT 0 supports 16 rx queues and 16 tx queues (driver_name = net_failsafe,
driver_type = 16)
PORT 0 is polling for link-change, interrupts disabled
[DPDK] tap_flow_create(): Kernel refused
On 11/22/2021 3:53 PM, Gaëtan Rivet wrote:
Could describe in more detail the execution?
In particular, setting the EAL log-level to debug with the option:
' --log-level pmd.net.failsafe:debug'
for example while using testpmd or your DPDK app.
It should show ethdev level accesses to the sub-device
On Mon, 14 Feb 2022 13:09:19 +
Vipul Ashri wrote:
> PORT 0 supports 16 rx queues and 16 tx queues (driver_name = net_failsafe,
> driver_type = 16)
>
> PORT 0 is polling for link-change, interrupts disabled
>
> [DPDK] tap_flow_create(): Kernel refused TC filter rule creation (17): File
> e
next reply if you are
still unsatisfied. GDB analysis will be bigger.
Thanks!
Regards
Vipul
-Original Message-
From: Gaëtan Rivet
Sent: Monday, November 22, 2021 3:53 PM
To: Vipul Ashri ; dev@dpdk.org
Cc: sta...@dpdk.org
Subject: [External] : Re: [PATCH v2] net/failsafe: link_update
On Thu, Oct 21, 2021, at 23:42, vipul.as...@oracle.com wrote:
> From: Vipul Ashri
>
> failsafe crashed while sending early link_update request during
> boot time initialization.
> Based on debugging we found failsafe device was good but sub-
> devices were progressing towards initialization and SU
On 10/21/2021 10:42 PM, vipul.as...@oracle.com wrote:
From: Vipul Ashri
failsafe crashed while sending early link_update request during
boot time initialization.
Based on debugging we found failsafe device was good but sub-
devices were progressing towards initialization and SUBOPS macro
where
From: Vipul Ashri
failsafe crashed while sending early link_update request during
boot time initialization.
Based on debugging we found failsafe device was good but sub-
devices were progressing towards initialization and SUBOPS macro
where expanding macro gives [partial_dev]->dev_ops->link_updat
10 matches
Mail list logo
