From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] 3 bugs for spp_pcap
Date: Wed, 20 Feb 2019 18:41:52 +0900 [thread overview]
Message-ID: <201902200944.x1K9iGN9015616@ccmail03.silk.ntt-tx.co.jp> (raw)
Hi,
I found the following bugs for spp_pcap.
1. Some packets can not be captured after pcap start.
2. Packet drop happens when receiving 64 byte short packet on 10Gbps
wire rate.
3. On receiving pcap stop command, packets are not flushed to files.
So when repeat capturing without shutdown of spp_pcap,
old packets are included in the capture file.
I will fix those bugs and report patches to this ML.
Sorry for inconvenience.
BR,
Hideyuki Yamashita
NTT TechnoCross
next reply other threads:[~2019-02-20 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 9:41 Hideyuki Yamashita [this message]
2019-03-12 5:02 ` Yasufumi Ogawa
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=201902200944.x1K9iGN9015616@ccmail03.silk.ntt-tx.co.jp \
--to=yamashita.hideyuki@po.ntt-tx.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@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).