DPDK usage discussions
 help / color / mirror / Atom feed
From: John Pearson <johnpearson555@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] KNI Integration
Date: Wed, 23 Nov 2016 10:40:21 -0800	[thread overview]
Message-ID: <CAKNtY_zxfqbQ5s-1TUObGB_VhQYXKsf9twdrkgZJbJmkEUJb0g@mail.gmail.com> (raw)
In-Reply-To: <CAKNtY_z0P+i4E6k7TWQEKaYJEMr6N0EvOkn995ONAs19UcbLPA@mail.gmail.com>

I tried to follow why the kni_config_network_function was being called
multiple times and it only happens sometimes. I have 4 cores and I am
running with coremask 0xf and lcores 0,1

On Fri, Nov 18, 2016 at 9:25 PM, John Pearson <johnpearson555@gmail.com>
wrote:

> Hi,
>
> I have a DPDK application with two interfaces acting as a load balancer.
> On one of the interfaces, I am allocating a KNI interface so that certain
> packets can be processed by the kernel. To test I have a DHCP server
> connected to the physical port to which KNI is bound.
>
> I'm having 3 issues:
>
> 1. kni_config_network_interface function set on the rte_kni_ops struct
> when allocating the port is called multiple times when run "ifconfig vEth0
> up".  This function is called 2 or 3 times every time.
>
> 2. After I receive DHCP, when I ping google.com to test, I get multiple
> packets that are duplicates, which are repeats of the same ICMP Sequence
> and with message "DUP!" attached (http://unix.stackexchange.com/a/13256)
>
> 3. After a while of running the interface KNI and using it process
> packets, usually after transmitting 200-300 Pings, the interface "dies out"
> and stops reading or sending packets to the kernel.
>
> The statistics for ping:
>
> --- google.com ping statistics ---
>
> 302 packets transmitted, 198 received, +95 duplicates, +49 errors, 34%
> packet loss, time 310119ms
>
>
>
>

      reply	other threads:[~2016-11-23 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19  5:25 John Pearson
2016-11-23 18:40 ` John Pearson [this message]

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=CAKNtY_zxfqbQ5s-1TUObGB_VhQYXKsf9twdrkgZJbJmkEUJb0g@mail.gmail.com \
    --to=johnpearson555@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).