DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lisowiec, Jan" <jan.lisowiec@intel.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] eRPC error
Date: Mon, 4 Nov 2019 20:47:58 +0000	[thread overview]
Message-ID: <83FB589E3555E04F82BDCB75936921E353B04FDE@IRSMSX107.ger.corp.intel.com> (raw)

Hi,

When using eRPC with DPDK the following error pops up:


69:828149 WARNG: Installing flow rule for Rpc 0. NUMA node = 0. Flow RX UDP port = 31882.
69:838908 WARNG: RawTransport created for Rpc ID 0. Device mlx5_0/enp175s0, port 1. IPv4 10.10.10.55, MAC 98:3:9b:63:e0:e0. Datapath UDP port 31882.
70:812503 WARNG: Installing flow rule for Rpc 2. NUMA node = 0. Flow RX UDP port = 31884.
70:813820 WARNG: RawTransport created for Rpc ID 2. Device mlx5_0/enp175s0, port 1. IPv4 10.10.10.55, MAC 98:3:9b:63:e0:e0. Datapath UDP port 31884.
Operation not permitted

Can anybody shed some light on what might be causing it ?

Thanks
Jan

--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
others is strictly prohibited.

                 reply	other threads:[~2019-11-04 20:48 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=83FB589E3555E04F82BDCB75936921E353B04FDE@IRSMSX107.ger.corp.intel.com \
    --to=jan.lisowiec@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).