From: PATRICK KEROULAS <patrick.keroulas@radio-canada.ca>
To: users@dpdk.org
Subject: [dpdk-users] mlx5: dual port capture
Date: Fri, 24 Jul 2020 17:04:20 -0400 [thread overview]
Message-ID: <CALEF-=B0_71ZpqT=3xqB9JUK+b5UC8hMBy3rRimnqNmB-XYffQ@mail.gmail.com> (raw)
Hello,
We use 2 physical networks for redundancy. In order to validate that
data on both network is similar, I need to capture traffic on the 2
NIC ports simultaneously, no matter if the result is 2 pcap files.
Since dpdk-pdump seems to work for one single port, I've tried to start
2 pdump processes simultaneously, which leads to a `Cannot reserve
memory` msg for one of these.
I'm not very familiar with how mem pools and queues work. But I feel
like there is a clever way to handle that. Can someone give a hint?
Best regards,
PK
next reply other threads:[~2020-07-24 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 21:04 PATRICK KEROULAS [this message]
2020-07-24 23:48 ` Stephen Hemminger
2020-07-30 19:06 ` PATRICK KEROULAS
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='CALEF-=B0_71ZpqT=3xqB9JUK+b5UC8hMBy3rRimnqNmB-XYffQ@mail.gmail.com' \
--to=patrick.keroulas@radio-canada.ca \
--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).