From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@amazon.com>,
Vincenzo Maffione <v.maffione@gmail.com>
Subject: Re: [Qemu-devel] [PULL 1/4] net: Adding netmap network backend
Date: Tue, 10 Dec 2013 10:49:00 -0700 [thread overview]
Message-ID: <52A7540C.8000006@redhat.com> (raw)
In-Reply-To: <1386594692-21278-2-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
On 12/09/2013 06:11 AM, Stefan Hajnoczi wrote:
> From: Vincenzo Maffione <v.maffione@gmail.com>
>
> This patch adds support for a network backend based on netmap.
> netmap is a framework for high speed packet I/O. You can use it
> to build extremely fast traffic generators, monitors, software
> switches or network middleboxes. Its companion software switch
> VALE lets you interconnect virtual machines.
> netmap and VALE are implemented as a non-intrusive kernel module,
> support NICs from multiple vendors, are part of standard FreeBSD
> distributions and available in source format for Linux too.
>
Sorry for not noticing sooner than the pull request, but:
> +++ b/qapi-schema.json
> @@ -3009,6 +3009,27 @@
> 'hubid': 'int32' } }
>
> ##
> +# @NetdevNetmapOptions
> +#
> +# Connect a client to a netmap-enabled NIC or to a VALE switch port
> +#
> +# @ifname: Either the name of an existing network interface supported by
> +# netmap, or the name of a VALE port (created on the fly).
> +# A VALE port name is in the form 'valeXXX:YYY', where XXX and
> +# YYY are non-negative integers. XXX identifies a switch and
> +# YYY identifies a port of the switch. VALE ports having the
> +# same XXX are therefore connected to the same switch.
> +#
> +# @devname: #optional path of the netmap device (default: '/dev/netmap').
> +#
> +# Since 1.8
s/1.8/2.0/
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-12-10 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 13:11 [Qemu-devel] [PULL 0/4] Net patches Stefan Hajnoczi
2013-12-09 13:11 ` [Qemu-devel] [PULL 1/4] net: Adding netmap network backend Stefan Hajnoczi
2013-12-10 17:49 ` Eric Blake [this message]
2013-12-11 8:39 ` Stefan Hajnoczi
2013-12-11 9:04 ` Vincenzo Maffione
2013-12-11 9:18 ` Stefan Hajnoczi
2013-12-09 13:11 ` [Qemu-devel] [PULL 2/4] MAINTAINERS: Add netmap maintainers Stefan Hajnoczi
2013-12-09 13:11 ` [Qemu-devel] [PULL 3/4] virtio-net: don't update mac_table in error state Stefan Hajnoczi
2013-12-09 13:11 ` [Qemu-devel] [PULL 4/4] net: Update netdev peer on link change Stefan Hajnoczi
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=52A7540C.8000006@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@amazon.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=v.maffione@gmail.com \
/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).