DPDK usage discussions
 help / color / mirror / Atom feed
From: DoHyung Kim <dohyung.kim@fluidic.io>
To: users@dpdk.org
Subject: Re: [dpdk-users] Weird phenomenon involving KNI
Date: Tue, 1 Jan 2019 19:04:45 +0900	[thread overview]
Message-ID: <CAH3X_xZSntX=pvqdSx5ywgV72t0e+ShNRu_WYn4jVaWF5Wu=gw@mail.gmail.com> (raw)
In-Reply-To: <CAH3X_xZAMrLUy1X5ktp3KmJ2Oxgz0ij832w6GEkbXwnas7k1eA@mail.gmail.com>

It was a consequence of the well-known behavior of Linux kernel regarding
ARP handling when multiple NICs are on the same subnet.

Thanks for all who have spent one's time looking into my question.

DoHyung


2018년 12월 31일 (월) 오후 6:42, DoHyung Kim <dohyung.kim@fluidic.io>님이 작성:

> I'm on the latest revision of 17.11 w/ a 2-port Intel X540 NIC. And having
> some trouble. one of the 2 ports is bound to a uio_pci_generic, and a KNI
> interface is up and assigned the MAC address of the port and an IP address,
> while the other port is kept intact bound to the kernel.
>
> Initially the 2 ports are known by their own IP addresses. But a few dozen
> seconds later, the latter port begins to report via ARP it has the IP
> address originally assigned to the KNI interface. So my DPDK app doesn't
> receive any of packets sent to the IP address assigned to the KNI interface.
>
> If I set the latter port down w/ ifdown and start my DPDK app, then my app
> receives packets as intended. But when I set the normal port up again, then
> it doesn't receive any packet since, this time, the KNI announces via ARP
> it has the IP address of the other port too.
>
> I searched for solution in DPDK mailing lists for this problem, but
> instead found a few posts mentioning KNI will be replaced w/ something
> else. But it seems that it's still gaining functionalities over the
> releases. So I'm confused.
>
> Please inform me of any clue for solving the problem described above. Or
> should I fallback to something more stable like TAP driver?
>
> Thanks in advance.
>
> --
> DoHyung Kim
> Fluidic Inc.
>


-- 
DoHyung Kim
Fluidic Inc.

  reply	other threads:[~2019-01-01 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31  9:42 DoHyung Kim
2019-01-01 10:04 ` DoHyung Kim [this message]
2019-01-02 12:38   ` Jay Rolette
2019-01-02 13:04     ` DoHyung Kim

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='CAH3X_xZSntX=pvqdSx5ywgV72t0e+ShNRu_WYn4jVaWF5Wu=gw@mail.gmail.com' \
    --to=dohyung.kim@fluidic.io \
    --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).