DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: MEMIF usage with dpdk-replay
Date: Mon, 21 Mar 2022 02:12:48 +0300	[thread overview]
Message-ID: <20220321021248.0fbe04c0@sovereign> (raw)
In-Reply-To: <CAO8pfFnZ4rUaJHFUVC2qsNUAPxGqq6Jhpp8+DNYdzBVh1eFLGw@mail.gmail.com>

Hi Antonio,

2022-03-20 16:35 (UTC+0100), Antonio Di Bacco:
> I'm using a dpdk-replay application (that reads from pcap and sends to a
> port) and I'm passing the parameter --vdev net_memif in order that the
> application sends packets to the memif PMD interface. Before launching
> dpdk-replay I launch the testpmd like this:
> 
> dpdk-testpmd -l 4-5 --proc-type=primary --file-prefix=pmd1 --vdev=net_memif

Do applications connect successfully?
Is dpdk-replay's memif configured with "role=server"?
Memif prints connection errors by default,
you can also rise log level: --log-level=pmd.net.memif:debug

      reply	other threads:[~2022-03-20 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 15:35 Antonio Di Bacco
2022-03-20 23:12 ` Dmitry Kozlyuk [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=20220321021248.0fbe04c0@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=a.dibacco.ks@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).