From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Merve Orakcı" <merveorakci58@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK-Pktgen big pcap files
Date: Sat, 5 Dec 2020 15:56:13 +0000 [thread overview]
Message-ID: <00EA150B-73EF-488B-972C-35C9D4C781AF@intel.com> (raw)
In-Reply-To: <CALtT+qahTgSdVaRc8-H+LTX0owUf8_uyXapOR_F7PJWP5aeiWg@mail.gmail.com>
> On Dec 5, 2020, at 4:36 AM, Merve Orakcı <merveorakci58@gmail.com> wrote:
>
> Hi everyboyd, I have 58 GB pcap file. I want to use this pcap file and send
> packet over DPDK port. For this reason, I use Pktgen tool but when i try to
> replay pcap file. pktgen aborted. This is about not enough memory for this
> pcap file? How should I adjust pktgen?
>
> root@lucky-X10SRA:/home/lucky# grep -i huge /proc/meminfo
> AnonHugePages: 0 kB
> ShmemHugePages: 0 kB
> HugePages_Total: 28
> HugePages_Free: 28
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 1048576 kB
Getting 58GB pcap file to be sent by Pktgen is going to be hard as the number of packet buffers currently allocated to Pktgen is not that huge. The other problem you have only have 28 hugepages. For Pktgen to use that large of file it needs to load all 58GB into memory and then we have to adjust the number of buffers that Pktgen allocates, which means changing the code. The PCAP file is somewhat compressed meaning packets are back to back and Pktgen would need (normally) a 2K buffer for even one 64 byte frame. So multiply the number of frames in the 58GB file with 2K and that is how much memory you would need to hold that 58K file.
Maybe some other tool is needed to send this large of a file. It appears I am not going to be much help here :-(
>
> --
> *Merve Orakcı*
> Research Asistant
> Gazi University - Institute of Informatics
> Computer Forensics
> Phone :+90 0312 202 3814
next prev parent reply other threads:[~2020-12-05 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 10:36 Merve Orakcı
2020-12-05 15:56 ` Wiles, Keith [this message]
2020-12-21 20:00 ` Merve Orakcı
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=00EA150B-73EF-488B-972C-35C9D4C781AF@intel.com \
--to=keith.wiles@intel.com \
--cc=merveorakci58@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).