DPDK usage discussions
 help / color / mirror / Atom feed
From: Gadre Nayan <gadrenayan@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] 10G vs 1G interface
Date: Fri, 17 Jun 2016 23:53:24 +0530	[thread overview]
Message-ID: <CAKJ7aR6pFdVXJbnG_N+qHdbebKe2jSeufswbNVCjRmPs-yn5eg@mail.gmail.com> (raw)

Hi,

Is there any distinction done when KNI interfaces come up for 10G vs 1G ports.

The ifconfig vEth0 down events are not handled reliably for 10G
interfaces. However, for 1G interfaces this works reliably. I get the
interface down events propagated correctly back to user space.

So, if I run ifconfig vEth0 down/up. The appropriate
rte_kni_ops.config_network_if

config_network_if = kni_config_network_interface (where it calls
start/stop functions.)

method is called, and there is no distinction done here for 10G vs 1G.

So where can I tweak the sources or any place elsewhere to get this
issue resolved.

Thanks.
,

                 reply	other threads:[~2016-06-17 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAKJ7aR6pFdVXJbnG_N+qHdbebKe2jSeufswbNVCjRmPs-yn5eg@mail.gmail.com \
    --to=gadrenayan@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).