From: Banashankar KV <banveerad@gmail.com>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: [dpdk-dev] Sending modified pcap packets from pktgen.
Date: Tue, 4 Feb 2014 18:51:41 -0800 [thread overview]
Message-ID: <CABkBM5HmNeW+MQwEaRxj=DT29qXxepLFYDZgWx5rPVSw9RF7OQ@mail.gmail.com> (raw)
Hi,
I am trying to send out modified pcap packets in a loop as shown below.I am
trying to modify source IP and source port.
for each *packet[12 in number]*
for each *sip[2 in number]*
for each *port[10 in number]*
change to *port *and *sip *in *packet*
ret = rte_eth_tx_burst(.....)
For the 6th packet, 80% of the packets sent out are same wrong packet and
other time i see the same other packet 2-3 times instead of the correct
packet. But if I place a breakpoint and send the packets one after the
other, all the packets have their respective modified port and source IP.
I am not able to figure out why it's behaving like this.
is there any caching of the packets or something like that?
In rte_mempool_create I see its passing 0 for cache size.
Thanks
Banashankar
next reply other threads:[~2014-02-05 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 2:51 Banashankar KV [this message]
2014-02-05 7:52 ` Wiles, Roger Keith
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='CABkBM5HmNeW+MQwEaRxj=DT29qXxepLFYDZgWx5rPVSw9RF7OQ@mail.gmail.com' \
--to=banveerad@gmail.com \
--cc=dev@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).