From: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
To: qemu-devel@nongnu.org
Cc: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>,
jan.kiszka@web.de, armbru@redhat.com, avi@redhat.com
Subject: [Qemu-devel] [PATCH RFC 0/4] Dumping traffic when using netdev devices
Date: Thu, 15 Jul 2010 17:22:56 -0300 [thread overview]
Message-ID: <1279225380-28790-1-git-send-email-miguel.filho@gmail.com> (raw)
Hello,
This is a prototype suggestion. I mostly copied and pasted the code from
net/dump.c into net.c and made some adjustments. There is no command line
parsing involved yet, just the internals and small changes in net/tap.c and
net/slirp.c do make the thing work.
In my tests, using tap as backend, e1000 as a guest device and running iperf from
guest to host, the overhead of dumping the traffic caused a loss of around 30%
of performance.
I opened the dumped files in wireshark and they looked fine. When using slirp
all requests were dumped fine too.
Bugs/limitations:
- I have no clue on how to deal with tap+vhost, is it necessary?
- When using virtio-net, I'm not sure how to handle iovec when vnet_hdr=on
- Create a function to add dump to a netdev on the fly, is it necessary?
- Handle cleanups
Miguel Di Ciurcio Filho (4):
net/dump: Make pcap structures public
net: Introduce NetClientDump and auxiliary functions
net/tap: Suggested support for NetClientDump
net/slirp: Suggested support for NetClientDump
net.c | 90 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
net.h | 8 +++++
net/dump.c | 21 -------------
net/dump.h | 21 +++++++++++++
net/slirp.c | 3 ++
net/tap.c | 3 ++
qemu-common.h | 1 +
7 files changed, 126 insertions(+), 21 deletions(-)
next reply other threads:[~2010-07-15 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 20:22 Miguel Di Ciurcio Filho [this message]
2010-07-15 20:22 ` [Qemu-devel] [PATCH RFC 1/4] net/dump: Make pcap structures public Miguel Di Ciurcio Filho
2010-07-15 20:22 ` [Qemu-devel] [PATCH RFC 2/4] net: Introduce NetClientDump and auxiliary functions Miguel Di Ciurcio Filho
2010-07-15 20:22 ` [Qemu-devel] [PATCH RFC 3/4] net/tap: Suggested support for NetClientDump Miguel Di Ciurcio Filho
2010-07-15 20:23 ` [Qemu-devel] [PATCH RFC 4/4] net/slirp: " Miguel Di Ciurcio Filho
2010-07-16 6:34 ` [Qemu-devel] Re: [PATCH RFC 0/4] Dumping traffic when using netdev devices Jan Kiszka
2010-07-16 14:39 ` Miguel Di Ciurcio Filho
2010-07-16 15:06 ` Jan Kiszka
2010-07-16 15:02 ` Anthony Liguori
2010-07-16 15:41 ` Markus Armbruster
2010-07-16 16:14 ` Anthony Liguori
2010-07-16 19:35 ` Miguel Di Ciurcio Filho
2010-07-16 15:45 ` Jan Kiszka
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=1279225380-28790-1-git-send-email-miguel.filho@gmail.com \
--to=miguel.filho@gmail.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.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).