All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1673] failed to parse device "net_pcap0"
Date: Wed, 12 Mar 2025 09:43:52 +0000	[thread overview]
Message-ID: <bug-1673-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1673

            Bug ID: 1673
           Summary: failed to parse device "net_pcap0"
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: 915768903@qq.com
  Target Milestone: ---

[Background Introduction]
   "I understand that the KNI feature was removed in DPDK version 23. I want
DPDK to load TAP devices to communicate with the kernel. The control-plane
packets [ICMP] received from the physical port should be handled by the TAP
devices <–vdev=net_tap0 –vdev=net_tap1>. After processing by DPDK, the
user-plane packets will be sent back to the physical port via DPDK’s TX
interface."

[To create a TAP device]
  sudo ip tuntap add dev dpdk_tap mode tap
  sudo ip link set dpdk_tap up
  sudo ip addr add 5.5.5.88/24 dev dpdk_tap 
[To create a TAP device]
    snprintf(option[opt_num++], 128, "dpdk_tap");
    snprintf(option[opt_num++], 128, "--main-lcore=%u", dns_cfg.mx_cpu);
    snprintf(option[opt_num++], 128, "--file-prefix=dpdk_tap");
    snprintf(option[opt_num++], 128, "-c0x%016llx%016llx%016llx%016llx",
            core_mask[3], core_mask[2], core_mask[1], core_mask[0]);
    snprintf(option[opt_num++], 128, "-n4");
    snprintf(option[opt_num++], 128, "--vdev=net_pcap0,iface=dpdk_tap");
    snprintf(option[opt_num++], 128, "--log-level=lib.eal:debug");
    dpdk_opt_info_get(&opt_num, option, &dns_cfg);
    dpdk_pci_info_get(&opt_num, option);

    int ret;
    if((ret = rte_eal_init(opt_num, option)) < 0)
    {
        printf("!error: rte_eal_init failed\n");
        return false;
    }

[Error message"]
EAL: Detected lcore 62 as core 12 on socket 0
EAL: Detected lcore 63 as core 12 on socket 1
EAL: Maximum logical cores by configuration: 128
EAL: Detected CPU lcores: 64
EAL: Detected NUMA nodes: 2
EAL: Checking presence of .so 'librte_eal.so.22.0'
EAL: Checking presence of .so 'librte_eal.so.22'
EAL: Checking presence of .so 'librte_eal.so'
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_pcap0"
EAL: Unable to parse device 'net_pcap0,iface=dpdk_tap'

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 4410 bytes --]

             reply	other threads:[~2025-03-12  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  9:43 bugzilla [this message]
2025-04-08 13:35 ` [DPDK/ethdev Bug 1673] failed to parse device "net_tap0" bugzilla

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=bug-1673-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.