From: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: avi@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] Re: [PATCH RFC 0/4] Dumping traffic when using netdev devices
Date: Fri, 16 Jul 2010 11:39:25 -0300 [thread overview]
Message-ID: <AANLkTinKTe-lm1KpVJSFEMI8dNptKlVucDRnJIIZKOj3@mail.gmail.com> (raw)
In-Reply-To: <4C3FFD88.5020305@web.de>
On Fri, Jul 16, 2010 at 3:34 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
>
>> - When using virtio-net, I'm not sure how to handle iovec when vnet_hdr=on
>
> Let the sending peer report (offset field or callback) where to find the
> payload in a frame.
>
Looking further, do you mean what net.c:vc_sendv_compat() does?
> That channel - or a separate one - could also be used to detect if a
> peer supports dumping at all (vhost...). Then no peer code need to be
> extended with dump management code, all could be moved into net.c
>
What do you mean by channel? (sorry, I'm kinda new around here :-)
I don't see how to put everything into net.c. Options parsing/setting
go inside each backend that adds a NetClientDump instance (just a few
lines as seen in my patch on net/tap.c as example), and when packets
come through net.c (qemu_deliver_packet_*()) we get them, right?
Regards,
Miguel
next prev parent reply other threads:[~2010-07-16 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 20:22 [Qemu-devel] [PATCH RFC 0/4] Dumping traffic when using netdev devices Miguel Di Ciurcio Filho
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 [this message]
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=AANLkTinKTe-lm1KpVJSFEMI8dNptKlVucDRnJIIZKOj3@mail.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).