From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B3C9C46AA0 for ; Mon, 30 Jun 2025 18:34:15 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 75E4C402A5; Mon, 30 Jun 2025 18:34:15 +0200 (CEST) Received: from mail-oa1-f51.google.com (mail-oa1-f51.google.com [209.85.160.51]) by mails.dpdk.org (Postfix) with ESMTP id 485AB4025D for ; Mon, 30 Jun 2025 18:34:14 +0200 (CEST) Received: by mail-oa1-f51.google.com with SMTP id 586e51a60fabf-2eff5d1c7efso1476417fac.2 for ; Mon, 30 Jun 2025 09:34:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751301253; x=1751906053; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=A36C/LAOMd8gP6yakXkckVptztFKFz1U4emNV0HEF/Q=; b=glOgZQcfxdGz2o56D3zakEa9ZLTEHLNrzhsLybxvoBN77eJZG/ofTuZzPksJqqVmQK ThXADtAsYnBLWn+LqbQ5gIlgMqb6UFo3lIy75rCO42I+kggUlK3r9bOYyuHwnAPIytDk +Xlo0pfG48YDSGKiEoooh8iIv/hA5eWTomVl4ojChEFAp1XwWgS2OVPgdMBWWQudMRUs hNikwE/XMYNneAJIvheLRoQLDLVfPp7nKo6cgketIr5p420rqzTEz410kCm5LAIhHYxt aPBeVwt8fMJ9psprpYWWQ+dkzLY7thMDZ82ICv7YncY23q/YEDM6cnJC2q1hVTjqaeIO 1SUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751301253; x=1751906053; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=A36C/LAOMd8gP6yakXkckVptztFKFz1U4emNV0HEF/Q=; b=TIOw0AWH1pE22EpxFGKQ1Z8sipl7Kb7iS1MkNJk8grRX/2mmyMZsSSEMYcNsIGGZW+ gKBdandZxXnM0xYLCWlKtia1m3++mgFZ5aIkL5alJ3RrkXilX9xm2C1s05aAjc9S8CgZ d36d2HiCrGVqp+R+2JfdkArvl6IElmhRQXycJuyfyDihrec+B7O9C1SApBUk1HZE0FRK ZZSzRMRW3HQIrgWITuUnePTD7rl8pQmoll80QHnk0FicLjVz6d88GQWOnLC6gL1oDwIJ EP2vE31V0l+y3tP0zIPKJjk94nr4ySpmidf5+vMFzZDBOn6d1gfErR3I+VH5BpK86ZK5 MsPw== X-Gm-Message-State: AOJu0Ywk1mh5b6cdWg0OeeZJnAkmEazF0TOclqO4xCsP9IN4h291n4Yo 5k+J1i3ty32NWtN10EUug4Apzr9JF3CotvK6ehpaTqPqWXo27bPhuFMTYALtxUgjO/4FSwj8Uz7 dUdU6awZ51LeMQRwQc7Mg3Zv1rIm5ti2B3nGZ X-Gm-Gg: ASbGncvTfmOAV7xnTZOxtO0nf/iG9XdZZI1P2wdcB5E9uXkbK44X8OwUQTkMgNrgDAx H6P7quLY8IsxHkSjTkrrSf2O69kkYkhwqZyo+JAygAAMDbKTHhAwcNXpH25aHHY23gIRMY1AkAt WycQa7vBGQ+iI7m30YFVb16Pa0g8Uem5Zy6DiM/lolBW30UHR3jjQaCooRq58Yk9VSObR4v+Gq2 +X7Ig== X-Google-Smtp-Source: AGHT+IHq7HAQjJLE80XvD9Utr+hX2GRe+9RVfQtkE3OBsnIvkSrn8/AlYxpZ1hgCN5gsNbiJ+/kKuDuwoIchZTnSqD0= X-Received: by 2002:a05:6870:8a1e:b0:296:bbc8:4a82 with SMTP id 586e51a60fabf-2efed70ae89mr10368961fac.27.1751301253189; Mon, 30 Jun 2025 09:34:13 -0700 (PDT) MIME-Version: 1.0 From: madhukar mythri Date: Mon, 30 Jun 2025 22:04:01 +0530 X-Gm-Features: Ac12FXyK_QJqbEydQby6JxdWT4heo7kTk2u2Cl_fKbkwnLg1iCLmC6ZJElkkMkk Message-ID: Subject: Seg-fault crash with the VF removal on Azure VM To: users Content-Type: multipart/alternative; boundary="000000000000175e480638cc99e5" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000175e480638cc99e5 Content-Type: text/plain; charset="UTF-8" Hi, We are facing a Seg-fault crash issue on our DPDK application with "failsafe" PMD on Azure VM, when we toggle the Azure "Accelerated networking" option. On the running VM, when we toggle(disable/enable) the "Accelerated networking" option, then we could see the respective SRIOV VF device was removed and added back, at this time our DPDK application got crashed while doing Rx "failsafe_rx_burst_fast()" operation. As per the DPDK "failsafe" PMD design the hotplug is supported and even after the primary SRIOV VF device is removed, the application can run Rx/Tx operations seamlessly on the other sub-device("netvsc"). But, this is not happening. Does anybody tested this hot-plug functionality on Azure VM and hot-plug works well on DPDK apps ? Any known issues/limitations on the "failsafe" PMD hot-plug ? DPDK-version: 23.11 Linux kernel-version: 5.15.0 Thanks, Madhukar. --000000000000175e480638cc99e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

We are= facing a Seg-fault crash issue on our DPDK application with "failsafe= " PMD on=C2=A0Azure= VM, when we toggle the Azure "Accelerated networking" option.


On the= running VM, when we toggle(disable/enable) the "Accelerated networkin= g" option, then we could see the respective SRIOV VF device was remove= d and added back, at this time our DPDK application got crashed while doing= Rx "failsafe_rx_burst_fast()" operation.


As per= the DPDK "failsafe" PMD design the hotplug is supported and even= after the primary SRIOV VF device is removed, the application can run Rx/T= x operations seamlessly on the other sub-device("netvsc"). But, t= his is not happening.


Does a= nybody tested this hot-plug functionality on Azure VM and hot-plug works we= ll on DPDK apps ?

Any kn= own issues/limitations on the "failsafe" PMD hot-plug ?


DPDK-v= ersion: 23.11

Linux = kernel-version: 5.15.0


Thanks= ,

Madhuk= ar.


--000000000000175e480638cc99e5--