DPDK usage discussions
 help / color / mirror / Atom feed
From: Igor de Paula <igordptx@gmail.com>
To: users@dpdk.org
Subject: help with virtio_port
Date: Tue, 23 May 2023 16:46:24 +0100	[thread overview]
Message-ID: <CALDr01RTzaBQUx0bW3gdsezB+Rm3d0ivqj8ugmZhjJu2hn0oAA@mail.gmail.com> (raw)

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

Hi,
I am running the DPDK version: 21.08.0 and Ubuntu 20.04.3 LTS.
I have an application that uses KNI to interface with the kernel.
I want to replace it with virtio_user ports as KNI will be deprecated in
the future.
Most of the functionality I am able to replace but there is one thing I am
struggling with.
In KNI we can add functions that will be called in case the network stack
makes a request. The following code shows this:
struct rte_kni *kni;
        struct rte_kni_conf conf;
        struct rte_kni_ops ops;
        struct rte_eth_dev_info dev_info;
        int ret;
        /* Clear conf at first */
        memset(&conf, 0, sizeof(conf));
        conf.core_id = 0;
        memset(&ops, 0, sizeof(ops));
        ops.port_id = ppo->id;
        ops.config_promiscusity = ippe_ppo_set_kni_promiscuous_mode;
        ops.change_mtu = ippe_ppo_set_kni_mtu;
        ops.config_network_if = ippe_ppo_set_kni_interface;
        ops.config_mac_address = ippe_ppo_set_kni_mac_address;
        kni = rte_kni_alloc(pktmbuf_pool[0], &conf, &ops);


And there is a handle_request function supplied by KNI that calls these
functions when need be,
I haven't found any documentation on how to replace this functionality. I
am no expert in how to set up and interact with the kernel stack, Some help
on how to achieve this would be appreciated.

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

             reply	other threads:[~2023-05-23 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 15:46 Igor de Paula [this message]
2023-05-23 16:23 ` Stephen Hemminger
2023-05-24 10:04   ` Igor de Paula
2023-05-27 10:04   ` Igor de Paula

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=CALDr01RTzaBQUx0bW3gdsezB+Rm3d0ivqj8ugmZhjJu2hn0oAA@mail.gmail.com \
    --to=igordptx@gmail.com \
    --cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).