DPDK usage discussions
 help / color / mirror / Atom feed
From: Renata Saiakhova <renata.saiakhova@ekinops.com>
To: "users@dpdk.org" <users@dpdk.org>, Haiyue Wang <haiyue.wang@intel.com>
Subject: [dpdk-users] Configure vlan interface on I350 Ethernet Controller Virtual Function
Date: Fri, 16 Jul 2021 15:19:10 +0000	[thread overview]
Message-ID: <MRZP264MB24423FAE9275FD717F96265992119@MRZP264MB2442.FRAP264.PROD.OUTLOOK.COM> (raw)

Hi all, hi Haiyue,

in our dpdk application I try to configure vlan interface on I350 Ethernet Controller Virtual Function.
As I understand I need to use two API calls :
rte_eth_dev_set_vlan_offload with an offload including ETH_VLAN_FILTER_OFFLOAD
and
rte_eth_dev_vlan_filter. The second one doesn't work without DEV_RX_OFFLOAD_VLAN_FILTER in dev->offloads, that's why the first call is needed to configure a vlan offload.
Here is the whole snippet:

   offload_mask = rte_eth_dev_get_vlan_offload(port_id);
   offload_mask |= ETH_VLAN_FILTER_OFFLOAD;
   diag = rte_eth_dev_set_vlan_offload(port_id, offload_mask);
   if (diag < 0) {
           printf("rx_vlan_filter_set(port_pi=%d, on=%d) failed "
                           "diag=%d\n", port_id, on, diag);
           return diag;
   }
   /* set vlan */
   diag = rte_eth_dev_vlan_filter(port_id, vlan_id, 1);
   if (diag < 0)
   {
           LO_ERROR("Error %d setting vlan filter, port %u", diag, port_id);
   }

However, rte_eth_dev_set_vlan_offload is not implemented for igbvf, dev_ops.vlan_offload_set is set to zero. For comparison, for ixgbevf vlan_offload is set to ixgbevf_vlan_offload_set.
Does the above mean, that it is not possible to configure vlan filter for igbvf by means of dpdk?

Kind regards,
Renata



             reply	other threads:[~2021-07-16 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 15:19 Renata Saiakhova [this message]
2021-07-18 13:29 ` Wang, Haiyue

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=MRZP264MB24423FAE9275FD717F96265992119@MRZP264MB2442.FRAP264.PROD.OUTLOOK.COM \
    --to=renata.saiakhova@ekinops.com \
    --cc=haiyue.wang@intel.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).